ASTRA Unified Research Lab MCP Server

tcai_memory_retrieve

Retrieve memories that align with a query by blending semantic similarity, PAD emotional congruence, and salience. Returns top-ranked memories for context or research.

Instructions

Retrieve memories by blended cosine similarity, PAD congruence and salience

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

Input Schema

Name	Required	Description
`topK`	No
`arousal`	No	Arousal ∈ [0,1]
`valence`	No	Pleasure ∈ [−1,1]
`dominance`	No	Dominance ∈ [0,1]
`embedding`	No	Query vector (defaults to current broadcast)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Aug 17, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are present, so the description bears the full burden. It discloses the scoring criteria but does not explain what happens when no memories match, whether the operation is read-only, the format of returned data, or what 'blended' and 'salience' mean. 'Retrieve' implies read-only, but explicit side-effect disclosure is absent.

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?

The description is a single sentence, front-loaded with the verb, and contains no redundant or filler words. It is appropriately concise for a retrieval operation.

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?

The tool has 5 optional parameters, no output schema, and no annotations. The description does not mention return values, default behavior for missing parameters (only embedding has a documented default in schema), or how topK bounds results. This is insufficient for a retrieval tool where callers need to know what to expect back.

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 80% (4 of 5 parameters have descriptions). The description adds context by linking PAD congruence to the arousal/valence/dominance parameters, but topK remains undocumented in both schema and description. The description does not add syntax or format details beyond what the schema provides, so a baseline 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?

The description uses a specific verb 'Retrieve' with resource 'memories' and explicitly names the retrieval criteria: 'blended cosine similarity, PAD congruence and salience'. This clearly distinguishes it from sibling tools like tcai_memory_store (store) and wm_* (working memory) tools.

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 is provided on when to use this tool versus alternatives. The sibling list includes several memory-related tools (tcai_memory_store, wm_encode, wm_recall, etc.), but the description does not mention any exclusions, prerequisites, or comparison to other retrieval mechanisms.

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

Deploy Server