Skip to main content
Glama

Inspect memory lineage

inspect_memory
Read-only

Use this when exact details or provenance matter: when the user asks why the assistant believes something, or wants to see the source memories behind a reflection. Given a memory id from a search result, returns the lower-tier memories that reflection was built from, or, for a raw memory, which reflections it was consolidated into. Use repeatedly to drill down from a high-level reflection to the tier 2 reflections and raw memories beneath it. Read only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "memory_id": "<memory_id>"
    },
    "name": "inspect_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
memory_idYesA memory id (UUID) from a search result or a previous inspect.

Output Schema

NameRequiredDescriptionDefault
tierYes
coversYes
sourcesYes
memory_idYes
truncatedYes
sources_totalYes
sources_deletedYes
consolidated_intoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint false, and openWorldHint false, so the closing 'Read only' sentence adds nothing. What does add value is the disclosure that traversal is bidirectional (down for reflections, up for raw memories) and that calls can be chained to walk the lineage, though nothing is said about what happens for an invalid or deleted memory id.

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 sentences, front-loaded with the decision condition ('when exact details or provenance matter') before the mechanism. Dense but nearly every clause carries information; only the trailing 'Read only' is redundant against the annotations.

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 one-parameter read tool with a full output schema and complete annotations, the description covers when to use it, what it returns conceptually, and the iterative drill-down pattern. Only edge-case behavior for missing or invalid ids is unaddressed, which is minor.

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% and the single memory_id parameter is already documented as a UUID from a search result or previous inspect, which the description largely repeats. Baseline 3 applies since the schema carries the parameter semantics.

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 and precisely describes both directions of traversal: for a reflection it returns the lower-tier memories it was built from, and for a raw memory it returns the reflections it was consolidated into. This distinguishes it clearly from sibling tools such as search_memories and consolidate_memories.

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?

Gives explicit triggering conditions – when the user asks why the assistant believes something, or wants provenance behind a reflection – and adds the iterative pattern of drilling down tier by tier. It does not explicitly name a contrasting sibling tool or state when not to use it, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources