emem, the verifiable memory protocol for the physical world

Open one search result and read the signed record

fetch

Idempotent

Dereference an id from search: the reading in one line, then the signed body it came from, the URL serving those bytes, and metadata naming cell, band, signing time and key. Takes an emem:fact: citation, a bare fact_cid, or an emem:cell: handle for a whole cell. The value is quoted as the exact decimal string it was signed as, never re-rendered. A fact handle writes nothing; a cell handle, like emem_recall, MATERIALIZES a missing band on a cold cell (fetched upstream, signed, persisted), so the flags follow that path: readOnlyHint false.

When to use: Call on each result you intend to cite, before quoting the number. Quote the one-line reading; the body makes it checkable, and emem_echo_verify grades what you emit against it. An oversize body says so inline and names the URL serving it whole.

Example arguments: {"id":"emem:fact:defi.zb493.xoso.zcb6a:cxjiu7l54ujzrpnekp24n4534yojpue4mprddbvevnqtti3lh5bq"}

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	An id from `search`: an `emem:fact:` citation, a bare fact_cid, or an `emem:cell:` handle for every fact at one cell.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Echoed id, in canonical form.
`url`	Yes	Stable URL serving these bytes.
`text`	Yes	The reading in one line, then the signed body it was lifted from. If the body was too large for the wire it says so inline, with the URL that serves it whole.
`title`	Yes	What this record is.
`metadata`	No	cell, band, when it was signed and by which key: the fields a reader needs to judge the citation without re-fetching it.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 13, 2026

TDQS

A5/5.0

Behavior5/5

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

Goes well beyond annotations: it explains the readOnlyHint=false flag by disclosing that cell handles can MATERIALIZE a missing band (fetched upstream, signed, persisted), while fact handles write nothing. It also reveals exact-decimal quoting, never re-rendering, and inline oversize-body behavior. No contradiction with 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?

Front-loaded with the core purpose, then compactly covers usage, side effects, and an example. Every sentence earns its place; no filler or repetition of the title or schema. The length is justified by the tool's behavioral complexity.

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, the description appropriately focuses on selection and invocation semantics. It covers the id format, the effect of each handle type, when to call it, what to quote, and how oversize bodies are reported. Nothing needed for correct invocation 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?

Even though schema coverage is 100%, the description adds substantial meaning beyond the schema: it explains the three accepted id forms and the behavioral difference between fact and cell handles, including the write path. This directly helps an agent choose the correct argument form and anticipate side effects.

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 ('Dereference'), the exact resource (an id from search), and the returned components (reading, signed body, URL, metadata). It clearly differentiates itself from search (which lists results) and from emem_recall/emem_echo_verify by naming them and describing its distinct role.

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 when to call it: 'Call on each result you intend to cite, before quoting the number.' It also gives the alternative context by distinguishing fact handles (writes nothing) from cell handles (materializes like emem_recall) and references emem_echo_verify for verification.

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

All emem, the verifiable memory protocol for the physical world tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.