Skip to main content
Glama

Recall memory

recall

Search stored preferences, lessons, and recent matching interactions before starting a task to adapt to the user's context.

Instructions

Search preferences + lessons via full-text index, plus recent matching interactions. Use before starting a new task.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax preference/lesson matches (default 8)
topicYesTopic to recall from memory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.2.1

TDQS

A3.7/5.0
Behavior3/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; it does disclose the sources consulted (a full-text index over preferences and lessons, plus recent matching interactions), which implies a read-only lookup. It does not say how results are ranked, how 'recent' is bounded, or how the two result sets are combined, which matters for a tool that merges sources.

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 short sentences with zero filler; the resource scope is front-loaded and the usage hint follows. Nothing is repeated from the title beyond what is needed.

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?

For a two-parameter, no-annotation, no-output-schema tool, the description covers the core purpose but omits result shape and ranking behavior, which the agent cannot learn from structured fields. Adequate, but an agent cannot predict what the returned matches look like or when 'recent' items appear.

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 100%, so both parameters are already documented in the schema. The description adds only that matching is full-text over preferences and lessons and that 'limit' caps preference/lesson matches, which is a marginal clarification rather than new meaning.

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 (search/recall) and concrete resources (preferences, lessons, recent matching interactions), which is far more informative than the bare name 'recall'. It does not explicitly contrast itself with close siblings like search_history or get_recent_interactions, so an agent must infer the boundary.

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?

'Use before starting a new task' gives a concrete application context that tells the agent when to reach for this tool. However, with 15 siblings including search_history and get_recent_interactions, no alternative or when-not condition is named, leaving overlap unresolved.

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