Skip to main content
Glama

recall

Looks up the retrieval path of a similar previously answered question to reuse prior search trajectories before searching, returning node texts, read hints, or a miss.

Instructions

Look up the retrieval path of a similar question answered before. Call it first, with the user's question copied verbatim (not rephrased or reduced to keywords). Returns mode=prefetch (node texts included), hint (node ids to read first) or miss (search).

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": "recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
budget_tokensNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No output schema exists, yet the description discloses the three possible return shapes — prefetch with node texts included, hint with node ids to read first, and miss — which is genuinely useful behavioral context an agent cannot get from the schema. It does not explain cost, latency, or whether state is mutated, which is notable since annotations declare readOnlyHint=false and idempotentHint=false for what reads like a lookup.

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?

Three short sentences, each carrying distinct information: what it does, how to call it, and what comes back. The ordering instruction is front-loaded and there is no filler.

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

Completeness4/5

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

For a two-parameter lookup with no output schema, the description covers purpose, invocation form, and return modes well enough to call it correctly. The remaining gap is budget_tokens, whose effect on results or truncation is never described.

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 description coverage is 0%, so the description must carry the load. It adds real meaning for 'query' (verbatim copying, no rephrasing, no keyword extraction) but says nothing about 'budget_tokens' (default 1500), leaving one of two parameters completely opaque.

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?

States a specific action and object: 'look up the retrieval path of a similar question answered before.' The concept is slightly jargon-y ('retrieval path'), but an agent can tell this is a memory/history lookup rather than a write. It does not explicitly name how it differs from the 'record'/'reject' siblings, keeping it below a 5.

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

Usage Guidelines4/5

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

Gives strong invocation guidance: call it first, and pass the user's question verbatim rather than rephrased or keyword-reduced. The 'miss (search)' outcome implies a fallback path without naming a search tool explicitly. No exclusion conditions are stated.

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

Deploy Server

Other Tools