CarryMem

Overview Schema Source Related Servers Discussions Admin

recall_memories

Retrieve stored memories with filtering by type, tier, and confidence. Supports full-text search to recall specific information.

Instructions

Retrieve stored memories. Supports filtering by type, tier, and confidence. Supports full-text search. Requires storage adapter.

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": "recall_memories"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of results (default 20)
`query`	No	Search query for full-text search (optional)
`filters`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Jun 20, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided. Description implies read-only but does not disclose behavior like result ordering, pagination limits, or error handling. Minimal behavioral context beyond basic retrieval.

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?

Two sentences, 18 words, no redundancy. Efficient but lacks depth; could include key details without adding bulk.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema; description omits return format, sorting, or pagination details. For a retrieval tool, this is insufficient for agents to interpret results correctly.

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 67%; description summarizes existing parameter roles (filtering, full-text search) but adds no new meaning beyond what the schema descriptions state. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Verb 'Retrieve' + object 'stored memories' clearly states action and resource. Differentiates from siblings like recall_all by specifying filtering and full-text search support.

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?

No guidance on when to use this vs alternatives (e.g., recall_all, recall_from_knowledge). Only mentions prerequisite 'Requires storage adapter', but no context on when filtering is appropriate.

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