Skip to main content
Glama

recall

Search stored memory to find ranked notes by query, project, and limit, returning titles, IDs, and snippets. Use read_note to open the full text of a matching note.

Instructions

Search memory. Returns up to 8 ranked hits as title, id and a short snippet. Use read_note for the full text.

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
limitNoMax hits (default 8, hard cap 8).
queryYes
projectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses result cardinality and format (up to 8 ranked hits: title, id, snippet) and that results are relevance-ranked, but says nothing about read-only nature, search scope across projects, or behavior when nothing matches.

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, front-loaded with the purpose, then the return contract, then the handoff. Every sentence carries information and nothing is wasted.

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 three-parameter search tool with no output schema, the description covers purpose, result shape and the follow-up tool, which is most of what an agent needs. The remaining gap is the undefined `project` filter and the nature of the matching, which leaves some ambiguity about search scope.

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 only 33%: `query` and `project` have no schema descriptions at all. The description reinforces the 8-hit cap already stated in the `limit` schema but adds no meaning for `query` (keyword vs semantic) or `project` (what it filters), so it does not compensate for the coverage gap.

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?

"Search memory" states a specific verb and resource, and the second sentence defines the return shape (up to 8 ranked hits with title, id, snippet). It distinguishes itself from read_note by scoping itself to search rather than full-text retrieval, though it does not differentiate from other siblings like list_notes or get_backlinks.

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?

The description gives one explicit routing rule: "Use read_note for the full text," which implies recall is the discovery step and read_note the retrieval step. It offers no guidance on when not to use it, no mention of how `project` narrows scope, and no alternatives for browsing rather than searching.

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