Skip to main content
Glama

memory_recall

Read-only

Retrieve named memories and linked wiki entries within a token budget, reporting unknown names as missing instead of failing.

Instructions

Read the named memories plus the memories they link to with [[wiki-links]], trimmed to a token budget. Unknown names are reported as missing instead of failing.

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": {
      "requires": "<requires>"
    },
    "name": "memory_recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
requiresYesMemory names to start from.
link_depthNoHow many [[link]] hops to follow. Default 1.
budget_tokensNoRough token budget for the result. Default 2000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower; the description still adds real value by disclosing that output is trimmed to a token budget and that unknown names surface as missing rather than raising an error. The one gap is it doesn't say what a 'missing' entry looks like or how trimming prioritizes content.

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?

Two tight sentences with no filler; the core behavior (read + follow links + budget) leads and the error-tolerance note follows as a secondary clause.

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?

There is no output schema, so the description carries the return-shape burden, and it does cover the two most important aspects: token-budget trimming and missing-name reporting. It stops short of describing the result structure (how memories and linked memories are organized), which would have made it fully self-sufficient for a three-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 100%, so requires, link_depth, and budget_tokens are already documented with defaults. The description reinforces the budget and hop concepts but adds no syntax, format, or edge-case detail (e.g. name matching rules, behavior at link_depth 0) beyond the schema, so the baseline 3 applies.

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 ('Read the named memories') and adds the distinguishing behavior of traversing [[wiki-links]] and trimming to a token budget. It does not explicitly name memory_get or memory_list to draw the boundary, but the graph-following scope is concrete enough that an agent can separate it from a plain single-memory getter.

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?

Usage is implied rather than stated: the link-traversal and budget language suggests it is the tool for pulling a cluster of related memories at once, but there is no explicit 'use this when... / use memory_get instead when...' guidance and no prerequisites mentioned.

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

This server cannot be deployed

Other Tools