Skip to main content
Glama
wusaki0723

Aelios

by wusaki0723
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

memory_get

Read-only

Fetch a single stored record by ID to view its full data and lifecycle fields before editing; read-only and returns not found if the ID is absent.

Instructions

Fetch one memory by id with its full record and lifecycle fields (fact_key, version status, superseded_by). Returns { data: record }, or an error result 'Memory not found' if the id does not exist in this namespace. Use it after memory_search, memory_recall or memory_list when you need the complete record before editing. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMemory id (e.g. from memory_search, memory_recall or memory_list).
namespaceNoMemory space to use. Defaults to 'default'. Ignored when the API key is bound to a fixed namespace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / id / description
      Added value: +"Memory id (e.g. from memory_search, memory_recall or memory_list)."
    • addedInput schema / properties / namespace
      Added value: +{
+  "description": "Memory space to use. Defaults to 'default'. Ignored when the API key is bound to a fixed namespace.",
+  "type": "string"
+}
  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 already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the 'Read-only.' trailer is largely redundant. The description still adds real behavioral context beyond annotations: the exact return shape { data: record } and the 'Memory not found' error outcome for a missing id in the namespace.

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?

Three tight, front-loaded sentences: return value first, then error case, then usage guidance. 'Read-only.' duplicates the readOnlyHint annotation and is the one sentence that does not fully earn its place.

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?

With no output schema, the description correctly compensates by naming the return envelope and the not-found error. Usage ordering and read-only status are also covered, leaving only minor things (e.g. behavior when the namespace is fixed by the API key) to the schema.

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%, so both id and namespace are already documented in the schema (including the fixed-namespace behavior). The description adds meaning for 'id' only indirectly ('in this namespace'), so 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?

States a specific verb and resource ('Fetch one memory by id') plus the payload it returns (full record with lifecycle fields fact_key, version status, superseded_by). The singular 'one memory' contrasts cleanly with the list/search siblings, so an agent can distinguish it without opening a schema.

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 specifies when to call it: 'after memory_search, memory_recall or memory_list when you need the complete record before editing.' It names the sibling alternatives and the condition that selects this tool, leaving no inference required.

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