Skip to main content
Glama

recall

Search indexed Claude Code conversations semantically to find matching turns with transcript path, line, and role, enabling quick context lookup.

Instructions

Recall past Claude Code conversations — semantic search over indexed chat turns.

Returns matching turns with their transcript path, line, and role (user/assistant).

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": {
      "text": "<text>"
    },
    "name": "recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
textYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations are absent, so the description carries the full burden, and it does add real behavioral detail: results are matching turns annotated with transcript path, line number, and role. It omits whether the operation is read-only (implied but unstated), whether a missing index degrades behavior, and whether results are ranked or truncated.

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 short sentences, front-loaded with the purpose and followed by the return shape; nothing is padded. Minor structural noise from the line break and indentation, but no wasted wording.

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?

The output schema explains the returned turn records, so the description need not re-document them, and for a two-parameter semantic search this coverage is adequate; the 'k' semantics gap is already counted under parameter semantics rather than a missing capability.

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

Parameters2/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 compensate, and it does not. Neither parameter is mentioned: 'text' is never identified as the semantic query, and 'k' is never explained as the result count despite defaulting to 5, which materially changes output volume.

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 verb and resource: semantic search over indexed chat turns from past Claude Code conversations. That is far more precise than the bare name 'recall'. It does not, however, contrast itself with siblings such as query, get, or search_code, so the agent must infer how this semantic recall differs from those.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given. 'Semantic search' hints at conceptual/fuzzy lookup, but the description never says to prefer this over a keyword query tool or a transcript getter, and it lists no prerequisites (such as needing an indexed corpus).

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