XMemo

Explain XMemo memory

explain_memory

Read-onlyIdempotent

Explains why a memory exists or matched a query whenever the user asks why something was saved there or why it was retrieved.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	No	Natural-language question or search text.
`memory_id`	Yes	Exact XMemo memory reference shown by search or recall.
`output_json`	No	Return a machine-readable JSON response instead of a human-readable summary.
`include_embedding`	No	Whether to include embedding/vector metadata in the returned explanation.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 11, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / include_embedding

Added value: +{
+  "default": false,
+  "description": "Whether to include embedding/vector metadata in the returned explanation.",
+  "title": "Include Embedding",
+  "type": "boolean"
+}

addedInput schema / properties / output_json

Added value: +{
+  "default": false,
+  "description": "Return a machine-readable JSON response instead of a human-readable summary.",
+  "title": "Output Json",
+  "type": "boolean"
+}

Changed3 schema fields changedJul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / include_embedding

Removed value: -{
-  "default": false,
-  "description": "Whether to include embedding/vector metadata in the returned explanation.",
-  "title": "Include Embedding",
-  "type": "boolean"
-}

removedInput schema / properties / output_json

Removed value: -{
-  "default": false,
-  "description": "Return a machine-readable JSON response instead of a human-readable summary.",
-  "title": "Output Json",
-  "type": "boolean"
-}

First observedJun 9, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, providing safety information. The description adds the two explanation modes (existence vs. retrieval match) but does not disclose additional behavioral traits such as how explanations are generated or any limitations. This is adequate but not rich.

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?

The description is a single, focused sentence that front-loads the core action and scope. No wasted words or redundant information.

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?

For a relatively simple, read-only tool with complete schema coverage, an output schema, and clear annotations, the description is largely sufficient. It could be slightly more complete by mentioning that it is complementary to recall/search tools, but the current text covers the essential use case.

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 the schema already documents all four parameters clearly. The description adds no extra parameter-level meaning, so the baseline of 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?

The description clearly states the tool's function: explaining why a memory exists or matched a query. This is a specific verb+resource definition that distinguishes it from sibling tools like recall (retrieval) and update_memory (modification).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit context for when to use the tool ('whenever the user asks why something was saved there or why it was retrieved'). However, it does not mention any when-not scenarios or alternative tools by name, so it falls short of full guideline coverage.

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

All XMemo tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.