Skip to main content
Glama

context_bundle

Combine note search with graph traversal in one call: get best-matching notes, their mentioned entities, and notes reachable within a specified number of hops.

Instructions

Search plus graph context in a single call. Returns the best-matching notes for the query, the entities those notes mention, and other notes reachable from those entities in up to hops steps.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "context_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
hopsNo
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the shape of the return (matched notes, their entities, and notes reachable via those entities), but says nothing about ordering, pagination, per-section result counts, or that it is a read-only operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core value proposition front-loaded. Minor awkwardness in 'in up to hops steps', and the sentence could more cleanly bracket the three return categories, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter tool with no annotations and no output schema, the description does reasonable work explaining the composite return, but leaves the limit parameter and result-count/ordering behavior undefined, which an agent would need to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It gives meaning to 'query' (drives best-match note selection) and 'hops' (graph traversal depth), but never mentions 'limit' or how it distributes across the three result sets, leaving one of three parameters undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific compound operation: search matching notes plus graph traversal from the entities those notes mention. It clearly distinguishes itself from a pure search by promising three result sets (notes, entities, reachable notes) in one call, though it never names a sibling tool it replaces.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Search plus graph context in a single call' implies the use case (when you want both recall and graph expansion without chaining calls), but there is no explicit when-to-use/when-not guidance or reference to alternatives like query_notes, search_brain, or related_notes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.