Skip to main content
Glama
Kaede Recall MCP

Kaede Recall MCP

memory-recall

Search long-term memories—facts, decisions, problems, and procedures—within a hard character budget, with filters and optional graph traversal to return relevant context.

Instructions

Search long-term memory (facts, decisions, problems, procedures) with a hard size budget.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "memory-recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoComma separated ids to open directly, skipping the search
kindsNoComma separated: fact,preference,profile,decision,problem,procedure,trace,doc
limitNoMax memories, default 5
queryNoWhat to look for, in the user's own words. Optional when ids is set
scopeNoExact scope, e.g. global or project:foo
projectNoProject id filter
max_charsNoHard cap for the block, default 3000
walk_depthNoFollow relations this many hops, default 0
include_supersededNoInclude replaced memories

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden; it mentions only a 'hard size budget' and does not state that the operation is read-only, how truncation works, or any permission or rate-limit constraints. The budget point is useful but largely repeats the max_chars schema field.

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?

One front-loaded sentence with no filler; every element (verb, resource, content types, budget) is relevant. It is appropriately sized for a terse search tool.

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 nine-parameter tool with no annotations or output schema, the description is very thin, but the schema richly documents each parameter. It is minimally complete about purpose, yet it does not explain return behavior or how the size budget affects results.

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 the schema documents all nine parameters including ids, kinds, scope, and walk_depth. The description adds only general content examples and the size-budget idea, which does not add much parameter-level meaning 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?

The description uses the specific verb 'Search' and resource 'long-term memory', and names example memory types such as facts, decisions, problems, and procedures. It does not explicitly contrast with siblings like memory-write or memory-update, so it is clear but not fully sibling-differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives no explicit 'use this when' guidance, exclusions, or alternatives; the closest is the implied use of searching memory. It also omits when to choose explicit ids versus a query, leaving the agent to infer usage from the schema.

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