Skip to main content
Glama

recall_with_graph

Read-onlyIdempotent

Search memory with Knowledge Graph expansion to retrieve connected context—related decisions, incidents, and learnings—ranked by composite score with hop distance and provenance.

Instructions

Search memory with Knowledge Graph expansion. Seeds from hybrid recall, then BFS-traverses memory_edges up to hops depth. Returns memories ranked by composite score with hop_distance and provenance fields. Returns broader context: related decisions, connected incidents, derived learnings. Slower and wider than recall: use it for the connected context around a topic, recall for a single fact.

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": {
      "q": "<q>"
    },
    "name": "recall_with_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query (keywords or natural language).
hopsNoGraph traversal depth (default 2, max 5).
task_idNoOptional task ID — used as cache key discriminator for session-scoped traversal.
project_idNoFilter to a specific project.
weight_thresholdNoMinimum edge weight to follow (default 0.3).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes further by disclosing the retrieval algorithm (hybrid seeding + BFS), the latency/width tradeoff versus `recall`, and the shape of results (composite ranking plus hop_distance and provenance). It does not discuss limits on graph size, truncation behavior, or how composite score is computed, which keeps it short of a 5.

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

Conciseness5/5

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

Four tight sentences, front-loaded with what it does and the mechanism, then the return shape, then the disambiguation. No filler and no repetition of the schema.

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

Completeness5/5

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

There is no output schema, yet the description still tells the agent what comes back (ranked memories with hop_distance and provenance, plus related decisions/incidents/learnings) and how cost differs from the cheaper sibling. Nothing needed to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by tying `hops` to BFS traversal depth over memory_edges and by explaining that `weight_threshold` governs which edges get followed and `task_id` acts as a cache discriminator. That is genuine semantics beyond the schema text.

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

Purpose5/5

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

States a specific verb+resource (search memory with Knowledge Graph expansion) and immediately explains the mechanism: seed from hybrid recall, then BFS over memory_edges to hops depth. It explicitly contrasts with the sibling `recall` (single fact vs. connected context), so an agent can pick between them without opening either schema.

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

Usage Guidelines5/5

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

The closing sentence gives an explicit routing rule: use this for connected context around a topic, use `recall` for a single fact, and notes it is slower and wider. That covers when-to-use, when-to-prefer-the-alternative, and the cost tradeoff in one line.

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