Skip to main content
Glama

recall

Ask your project's memory a plain-language question to retrieve relevant stored notes before scanning the codebase, with results labeled [project] or [shared].

Instructions

Ask the project's memory what it holds about a question, before you read the code base from scratch. It answers with the lines of this project's memory and the shared memory that share words with question, best first, each starting [project] or [shared]. Ask in plain words ("how do tests start the dev database"); a line remember_for_project kept earlier is found here. note says so when the cell's memory service did not answer and the Tares docs did.

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

Input Schema

NameRequiredDescriptionDefault
projectNo
questionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.59.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose real behavior: matching is by shared words rather than semantics, results are ordered best-first, each line is prefixed with its source scope, and there is a fallback path when the cell's memory service does not answer. It does not mention result limits or read-only safety, but as a retrieval tool the disclosed traits are the important ones.

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

Conciseness3/5

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

The usage constraint and the return-shape explanation are correctly front-loaded, and the parenthetical example earns its place. However the final sentence about `note` and the Tares docs is cryptic and reads as an afterthought that costs more attention than it returns.

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?

An output schema exists, so the return format and the `note` field need not be spelled out, yet the description still gestures at them ambiguously instead of relying on the schema. The main completeness gap is the entirely undocumented `project` parameter for a two-parameter tool.

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 compensate. It does well for `question` — plain-word phrasing, a worked example, and the fact that matching is token-based — but the `project` parameter is never mentioned at all, leaving the agent to guess whether it scopes the search or defaults to the current project.

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 states a concrete verb and resource: ask the project's memory what it holds about a question, returning matching lines tagged [project] or [shared], best first. It implicitly separates itself from the write-side sibling by noting that a line 'remember_for_project' kept earlier is what gets found here, but it never names an alternative retrieval tool or explicitly contrasts scope.

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?

Clear timing guidance: use it 'before you read the code base from scratch', which gives the agent a decision rule against a concrete alternative behavior. It also states the query style (plain words, with an example question). What's missing is an explicit when-not or a named sibling to defer to for other kinds of lookups.

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