Skip to main content
Glama
wusaki0723

Aelios

by wusaki0723
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

memory_recall

Recall relevant memories for a question using hybrid search, reranking, and min_score filtering, returning citable hits without altering memory content.

Instructions

Answer-oriented recall: matches glossary terms literally, runs hybrid search over active memories, reranks the hits and drops anything below min_score. Returns { data: { hits, glossary_hits, week_blocks, meta } }, each hit with id, score and source so you can cite or edit it. Precious entries are not searched here (they come from memory_boot). Prefer this over memory_search when you want only the relevant memories for the current question. Never changes memory content, but marks the returned memories as recently injected, which briefly lowers their rank in later automatic recall.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kNoMaximum number of memory hits. Defaults to 20.
queryYesThe question or topic to recall memories for.
typesNoOnly recall these memory types (fact, event, preference, relationship, boundary, habit, decision, note). Omit for all types.
min_scoreNoRelevance floor applied after reranking. Defaults to the server setting (0.15).
namespaceNoMemory space to use. Defaults to 'default'. Ignored when the API key is bound to a fixed namespace.
include_historyNoWhen true, include superseded memory versions (status/version_status=superseded). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.2
    • addedInput schema / properties / k / description
      Added value: +"Maximum number of memory hits. Defaults to 20."
    • addedInput schema / properties / min_score / description
      Added value: +"Relevance floor applied after reranking. Defaults to the server setting (0.15)."
    • addedInput schema / properties / namespace / description
      Added value: +"Memory space to use. Defaults to 'default'. Ignored when the API key is bound to a fixed namespace."
    • addedInput schema / properties / query / description
      Added value: +"The question or topic to recall memories for."
    • addedInput schema / properties / types / description
      Added value: +"Only recall these memory types (fact, event, preference, relationship, boundary, habit, decision, note). Omit for all types."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and non-idempotent, which is surprising for a 'recall' tool; the description resolves this by explaining it 'marks the returned memories as recently injected, which briefly lowers their rank in later automatic recall' — a genuine side effect beyond structured data. It also states the return shape and that precious entries aren't searched. It does not mention auth namespace binding edge cases, but the side-effect disclosure is the key non-obvious behavior.

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?

Four dense sentences front-load the core mechanism and return shape, then handle routing and side effects. No wasted words, though the return-shape enumeration and side-effect clause make it slightly long; every sentence carries distinct information.

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?

Covers mechanism, return structure, sibling routing, exclusion of precious entries, and the rank-injection side effect — comprehensive for a 6-param tool with no output schema. Minor gap: it doesn't explain namespace versus API-key binding interplay, but that is adequately handled by the schema description.

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 every parameter including k, types, min_score, namespace, and include_history is already documented in the schema with defaults and constraints. The description adds the pipeline context (min_score applied after reranking) but no syntax or format details the schema lacks. Baseline 3 is correct.

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?

Names a specific verb+resource ('recall memories') and details the exact pipeline: literal glossary matching, hybrid search over active memories, reranking, and min_score filtering. This is far more specific than siblings like memory_search, and the explicit 'Prefer this over memory_search when...' clause makes the distinction operational.

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

Usage Guidelines5/5

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

Explicitly states when to use it ('when you want only the relevant memories for the current question') and names the alternative (memory_search). It also carves out the precious-entry exclusion and notes memory_boot as their source, so the agent knows not to expect them here.

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

Deploy Server

Other Tools