aziel-runtime

Explain a memory

memory_get

Read-onlyIdempotent

Retrieve a memory's stored explanation by ID (node, history, or calibration). Use when you have a specific memory ID, not for ranked recall or observations.

Instructions

Read one memory's stored explanation (node, history, or calibration: posterior, triad legs, effective N, Brier) — not a ranked list. Use this when you have a memory_id (or id) and need the stored explanation. Do not use it for ranked adaptive recall or appending an observation; use memory_recall or memory_observe instead. Missing both memory_id and id, or an unknown id, refuses AKM-NOT-FOUND — do not invent a node. authorizes_action stays false. There is no memory_delete; this is the read of the append-only node. Pass memory_id or id — one is enough; they are aliases, not two different records. Omit view for the default node slice. history returns events/resolutions; calibration returns posterior/triad/Brier. subject is not a lookup key here. Returns node, history, or calibration view (belief_is_not_truth).

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Alias of memory_id. Do not send two different values.
`view`	No	Optional slice. Omit or get = stored node; history = events/resolutions; calibration = posterior, triad legs, effective N, Brier.
`memory_id`	No	Memory id to explain. Alternative to id. Missing both refuses AKM-NOT-FOUND.

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	FragGate or fabric code when present: FG-OK, FG-HALLUC-TOOL, FG-STUB, FG-LOCAL-ONLY, FG-UNKNOWN-OP, FG-GATE-REFUSE, FG-LAMB-REFUSE, or a module refuse such as MESH-* / AKM-*.
`door`	No	Door name. The public door is fraggate.
`ran_in`	No	Execution locale (for example aziel-runtime) when present.
`result`	No	Explain body: ok, memory_id, status, plus node or events or calibration fields. belief_is_not_truth. Refuses AKM-NOT-FOUND when the id is missing or unknown.
`status`	No	HTTP-like status when present on wrappers (200 ok; 400+ error / refuse).
`display`	No	Human-facing envelope. Show display.action, title, and summary, then take the next input. Never echo raw tool names.
`receipt`	No	Optional receipt, ledger tip, or TemporalLock/ForgeReceipts exit when the door stamped one.
`refusal`	No	Explicit refuse object, code, or message when the door or engine refused.
`engine_op`	No	Resolved engine op when present (often inside result).
`ledger_tip`	No	Ask/refuse ledger tip when the door stamped one.
`provenance`	No	Provenance / input packet when the pipeline attached one.
`session_id`	No	Raw session id when session plumbing was used. Hidden unless the user asked for the chain.
`engine_slug`	No	Resolved engine slug when present (often inside result).
`limitations`	No	Capability limitations or Remain-OFF notes when present.
`engine_digest`	No	64-hex engine_digest when a true in-process engine ran (often inside result).

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv2.0.9Sep 29, 2026

changedOutput schema / description

Previous value: -"Display envelope shown to the user (display.title / display.summary) plus the machine result. Extra engine fields may appear."New value: +"Display envelope shown to the user (display.action / display.title / display.summary) plus the machine result. Extra engine fields may appear. Do not echo raw tool names."

changedOutput schema / properties / display / description

Previous value: -"Human-facing envelope. Show title and summary, then take the next input."New value: +"Human-facing envelope. Show display.action, title, and summary, then take the next input. Never echo raw tool names."

addedOutput schema / properties / display / properties / action

Added value: +{
+  "description": "Human-visible run frame. Always \"Run aziel runtime\". Product verb titles stay on title. Not a tool name.",
+  "type": "string"
+}

addedOutput schema / properties / display / properties / image

Added value: +{
+  "additionalProperties": true,
+  "description": "Present only when a real production included png_b64, jpeg_b64 (or the same byte family), or a cited http(s) image URL. No invented thumbs. Omitted on dry_run. reviewed is true only when executed production bytes are attached; a dry_run never mints reviewed.",
+  "properties": {
+    "data": {
+      "description": "Base64 image bytes copied from the production. Omitted for a URL-only cite. Never present on dry_run.",
+      "type": "string"
+    },
+    "mimeType": {
+      "description": "Sniffed image media type (image/png, image/jpeg, image/webp, or image/gif).",
+      "type": "string"
+    },
+    "reviewed": {
+      "description": "True only when data came from an executed production. False for a URL cite without bytes. Never true on dry_run.",
+      "type": "boolean"
+    },
+    "source": {
+      "description": "Production field the image was taken from (for example png_b64, jpeg_b64, or image_url).",
+      "type": "string"
+    },
+    "url": {
+      "description": "Cited http(s) image URL when the production named one. Not invented.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

changedOutput schema / properties / display / properties / title / description

Previous value: -"Short result title for the AI client."New value: +"Product verb title for the AI client. Not a raw tool name."

Changed5 schema fields changedv2.0.1Sep 14, 2026

changedInput schema / description

Previous value: -"Pass memory_id or id. view selects the explain slice."New value: +"Pass memory_id or id (aliases). Omit view for the node slice. Extra properties are rejected."

changedInput schema / properties / id / description

Previous value: -"Alias of memory_id."New value: +"Alias of memory_id. Do not send two different values."

changedInput schema / properties / memory_id / description

Previous value: -"Memory id to explain. Alternative to id."New value: +"Memory id to explain. Alternative to id. Missing both refuses AKM-NOT-FOUND."

changedInput schema / properties / view / description

Previous value: -"Optional view: get (default node), history, or calibration."New value: +"Optional slice. Omit or get = stored node; history = events/resolutions; calibration = posterior, triad legs, effective N, Brier."

changedOutput schema / properties / result / description

Previous value: -"FragGate body: ok, code, door, slug, op, engine_digest, ran_in, provenance, refusal, limitations, receipt, plus the engine result. Unknown names refuse FG-HALLUC-TOOL; stubs refuse FG-STUB."New value: +"Explain body: ok, memory_id, status, plus node or events or calibration fields. belief_is_not_truth. Refuses AKM-NOT-FOUND when the id is missing or unknown."

Addedv1.6.2Sep 12, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already mark readOnly/idempotent/non-destructive, and the description adds failure behavior (AKM-NOT-FOUND refusal, no invented nodes), authorization side-effect (authorizes_action stays false), and append-only nature. This is exactly the contextual behavior an agent needs beyond annotations.

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?

Every sentence carries a distinct fact: purpose, when-to-use, error behavior, alias handling, view semantics. Despite length, it is front-loaded and dense with no filler.

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?

With an output schema present, return values need no elaboration; the description covers selection criteria, error/refusal, alias usage, and sibling routing. Nothing needed to invoke correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds alias semantics ('they are aliases, not two different records'), default view behavior ('Omit view for the default node slice'), and a negative lookup constraint ('subject is not a lookup key here'). This exceeds schema detail.

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 ('Read'), resource ('one memory's stored explanation'), and explicitly contrasts with 'not a ranked list', distinguishing it from memory_recall. The title 'Explain a memory' aligns and the description names the exact views returned.

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 says 'Use this when you have a memory_id (or id) and need the stored explanation' and 'Do not use it for ranked adaptive recall or appending an observation; use memory_recall or memory_observe instead.' Also notes there is no memory_delete, preventing misuse.

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