ASTRA

tcai_memory_store

Store an experience in attention-gated, salience-indexed emotional memory using valence, arousal, and dominance so agents can later recall salient events.

Instructions

Store an experience in emotional memory (attention-gated, salience-indexed)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "narrative": "<narrative>"
    },
    "name": "tcai_memory_store"
  }
}

Input Schema

Name	Required	Description
`arousal`	No	Arousal ∈ [0,1]
`valence`	No	Pleasure ∈ [−1,1]
`dominance`	No	Dominance ∈ [0,1]
`embedding`	No	Feature vector (defaults to current broadcast)
`narrative`	Yes	Description of the experience
`attentionLevel`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.1.0Sep 23, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false), so the description needn't restate them. It adds 'attention-gated, salience-indexed', which hints that storage may be suppressed by low attention and that entries carry a salience index, but this is cryptic jargon rather than an operational explanation.

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?

A single compact phrase with no waste, and the core action is front-loaded. It is arguably too terse for the tool's complexity, but it is efficient and non-redundant.

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 6-parameter write tool with no output schema, the description is thin: it never says what 'attention-gated' means operationally, whether a store can silently fail, or what is returned. Annotations cover the safety profile and the schema covers most params, but behavioral completeness is only marginally adequate.

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 83%, so the schema already documents arousal/valence/dominance ranges, embedding defaults, and narrative. The description adds nothing about parameter meaning (e.g., that attentionLevel drives the 'attention-gated' behavior). Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb (Store) and resource (an experience in emotional memory), with the parenthetical scope hint 'attention-gated, salience-indexed'. It is clearly a write counterpart to tcai_memory_retrieve, though the description never names that sibling to make the distinction explicit.

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?

There is no when-to-use, when-not, or prerequisite guidance. An agent must infer from the name that this is the write path versus tcai_memory_retrieve, and nothing indicates conditions like required attention level or failure modes.

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

Deploy Server