aziel-runtime

ChainLock recall

chainlock_recall

Read-onlyIdempotent

Instructions

Grounded ChainLock recall at depth 0–5 (id+h+fh facts or refuse=no-stamp). Stamped vault facts — not Bayesian rank and not tip-only. Use this when you need stamped facts from the local vault, not a Bayesian ranking. Do not use it for adaptive memory ranking or reading only the live tip; use memory_recall or chainlock_tip instead. Depth above 5 is clipped to 5. refuse=no-stamp when empty — do not invent a fact. Append-only; there is no chainlock_delete. Omit depth to use 1 (not 0). 0 = tip only; 5 = full chain / genesis budget. Omit c/chain to scan session+acts+recall+learn (not the whole roster). q/query is a case-insensitive subject/fact substring; empty q does not invent cards. Returns grounded facts (id, h, fh) or refuse=no-stamp.

Input Schema

TableJSON Schema

Name	Required	Description
`c`	No	Optional chain name. One of genesis, identity, ssh, session, acts, evidence, recall, mesh, library, learn. Alias: chain. Omit both to scan session, acts, recall, and learn — not the full roster.
`q`	No	Optional case-insensitive substring over subject/fact. Alias: query. Empty does not invent matches.
`chain`	No	Alias of c. Omit both to scan session, acts, recall, and learn — not the full roster.
`depth`	No	Optional recall depth. Omit for 1. 0 = tip only; 5 = genesis/budget maximum. Values outside 0–5 are clipped. Alias: d.

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	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.
`status`	No	HTTP-like status when present on wrappers (200 ok; 400+ error / refuse).
`display`	No	Human-facing envelope. Show title and summary, then take the next input.
`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.1Sep 14, 2026

changedInput schema / description

Previous value: -"All fields optional. depth is 0 (tip) through 5 (genesis/budget)."New value: +"All fields optional. Default depth is 1. Default chains are session, acts, recall, learn."

changedInput schema / properties / c / description

Previous value: -"Optional chain name to recall from. Omit to use the default recall path."New value: +"Optional chain name. One of genesis, identity, ssh, session, acts, evidence, recall, mesh, library, learn. Alias: chain. Omit both to scan session, acts, recall, and learn — not the full roster."

addedInput schema / properties / chain

Added value: +{
+  "description": "Alias of c. Omit both to scan session, acts, recall, and learn — not the full roster.",
+  "enum": [
+    "genesis",
+    "identity",
+    "ssh",
+    "session",
+    "acts",
+    "evidence",
+    "recall",
+    "mesh",
+    "library",
+    "learn"
+  ],
+  "type": "string"
+}

changedInput schema / properties / depth / description

Previous value: -"Optional recall depth. 0 = tip only; 5 = genesis/budget maximum. Values outside 0–5 are clipped."New value: +"Optional recall depth. Omit for 1. 0 = tip only; 5 = genesis/budget maximum. Values outside 0–5 are clipped. Alias: d."

changedInput schema / properties / q / description

Previous value: -"Optional query string to filter recalled cards. Does not invent matches."New value: +"Optional case-insensitive substring over subject/fact. Alias: query. Empty does not invent matches."

Addedv1.6.2Sep 12, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations declare readOnly/idempotent/non-destructive, and the description adds behavior beyond them: depth above 5 is clipped, empty results return refuse=no-stamp rather than fabricated facts, the store is append-only with no delete counterpart, and the default depth/chain-scan scope is spelled out. The empty-result and clipping semantics are exactly the kind of non-obvious behavior an agent needs.

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?

Front-loaded with purpose then scope, alternatives, then parameter defaults. It is dense and slightly run-on with many dashes and clauses, but nearly every sentence carries a distinct constraint rather than 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?

An output schema exists, so return-shape explanation is not required; the description nonetheless covers defaults, clipping, empty-result behavior, and chain-scan scope. For a 4-param, fully-optional read tool, nothing needed to call it correctly is missing.

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% and the schema already documents defaults, aliases, clipping, and the 0/5 meaning of depth, so the description's restatement of these earns little. It does frame the depth range semantically (tip only vs full chain/genesis budget), but that is largely duplicative of the schema text; baseline 3 applies.

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+resource with scope ('Grounded ChainLock recall at depth 0–5') and explicitly contrasts itself with the two nearest siblings: it is not 'Bayesian rank' and not 'tip-only'. An agent can distinguish it from memory_recall and chainlock_tip without opening either 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?

Gives explicit when-to-use ('when you need stamped facts from the local vault') and when-not (adaptive memory ranking, reading only the live tip), naming the alternative tools to use instead. This is the full when/when-not/alternatives pattern.

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