Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

recall_context

Retrieve previously saved context from the cache. Returns the saved content or null if not found. Use this at the START of any task to check if you already have relevant context cached, before doing expensive operations like reading many files. Supports glob patterns: "file:" matches all file summaries, "arch" matches architecture-related keys.

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": {
      "key": "<key>"
    },
    "name": "recall_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe key to look up (supports glob pattern like "file:*")
instance_idNoUUID of the cache instance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 discloses the miss behavior (returns null) and glob matching semantics, which is genuinely useful. It does not say whether this is a pure read with no side effects, whether hits are recorded or entries refreshed, whether cached content can be stale, or what happens when the optional instance_id is omitted — gaps that matter for a cache-read tool.

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?

Front-loaded with purpose, then return value, then usage timing, then pattern semantics — a sensible order with no filler sentences. The glob explanation partially restates the schema's glob note, which is a small redundancy.

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?

No output schema exists, and the description covers the return contract (content or null) as well as invocation timing and pattern support. Remaining gaps are secondary: staleness of cached entries and the meaning of the optional instance_id parameter.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning: it names the key namespaces in use ('file:*' for all file summaries, 'arch*' for architecture-related keys), telling the agent what a glob will actually match. The optional instance_id is not described beyond the schema.

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?

Clear specific verb and resource: retrieval of previously saved context from a cache, including the null-on-miss outcome. It does not distinguish itself from plausible siblings such as cache_get, smart_recall, or team_recall, so an agent cannot tell from the description alone which recall variant to pick.

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?

Explicit timing guidance: use at the START of a task before expensive operations like reading many files. This gives a concrete condition for invocation. It lacks any when-not guidance or named alternatives, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.