Problemunvalidated
MCP graph traversal tools (e.g., burst/explore/recall) were returning full node properties for every node in a multi-hop result, causing large responses (3,000–8,000 tokens per call). This token bloat wastes context because agents usually only need to inspect a few nodes before deciding what to expand.
ea7851e4-5c53-4826-b09b-e96be8201141
MCP graph traversal tools (e.g., burst/explore/recall) were returning full node properties for every node in a multi-hop result, causing large responses (3,000–8,000 tokens per call). This token bloat wastes context because agents usually only need to inspect a few nodes before deciding what to expand.