Skip to main content
Glama
CodeAbra

iai-mcp

memory_recall

Read-onlyIdempotent

Recall stored memories by matching a natural-language cue. Retrieves relevant hits and anti-hits with validity dates for context-aware memory access.

Instructions

Recall verbatim memories by cue. Returns hits + anti_hits with derived valid_from/valid_to. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cueYesNatural-language query to match against stored memories. Embedded server-side via bge-small-en-v1.5 (384d) unless `cue_embedding` is supplied.
budget_tokensNoSoft token budget for the response (default 1500). Hits are appended until the next would exceed this budget; at least one hit is always returned.
session_idNoCurrent session id; gets written into every recalled record's provenance. Omit to use '-'.
cue_embeddingNoOptional pre-computed embedding vector for the cue (EMBED_DIM=384 floats; bge-small-en-v1.5). When omitted, the daemon embeds the cue server-side. Used by memory_contradict and tests that need byte-stable embeddings.
languageNoOptional ISO-639-1 language hint for the sleep-suggestion path (8 supported: en/ru/ja/ar/de/fr/es/zh). Defaults to 'en' when omitted. Hot-path retrieval is language-agnostic; this key only affects the sleep-suggestion regex pre-screen.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsNo
anti_hitsNo
activation_traceNo
budget_usedNo
hintsNo
cue_modeNo
patterns_observedNo
Behavior4/5

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

Description adds context beyond annotations: it specifies that results include hits and anti_hits with derived valid_from/valid_to. It reaffirms read-only behavior, aligning with annotations. No contradictions.

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 brief sentences front-load the purpose and key behavioral notes. No extraneous content; every sentence earns its place.

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

Completeness5/5

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

Given full schema descriptions and an output schema, the description is complete. It covers the tool's role, return types, and safety profile, enabling an agent to determine when to invoke it.

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%. The description does not add extra meaning to parameters beyond what the schema provides, achieving the baseline score of 3.

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?

Description clearly states the core function: recalling verbatim memories by cue. It mentions returning hits and anti_hits with derived timestamps, and distinguishes it from siblings like memory_recall_structural and memory_contradict by the term 'verbatim' and specifying read-only nature.

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?

The description implies this tool is for reading memories with read-only hint, but does not explicitly state when to use it over siblings like memory_recall_structural or memory_contradict. No exclusions or alternative guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CodeAbra/iai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server