Skip to main content
Glama

memory_detail

Read-only

Retrieve ranked details for a single entity, including its memory chunks and related entities, to drill into one item from a knowledge map.

Instructions

Get the full ranked detail for a single entity.

USE THIS WHEN:

  • User drills into one entity from a knowledge map ("tell me more about X")

  • Need the full ranked list of chunks for an entity plus its related entities

Returns:

  • entity_id, name

  • chunks: ranked memory chunks (relevance now; composite_score + score_components once #55 lands)

  • related_entities: neighbouring entities (gated by include_related / max_hops)

Read-only.

Examples: {"entity_id": "authentication-design"} {"entity_id": "python", "limit": 20, "include_related": false} {"entity_id": "database", "max_hops": 2}

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": {
      "entity_id": "<entity_id>"
    },
    "name": "memory_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum ranked chunks to return
storeNoOptional store/namespace to scope retrieval (composes with multi-store support)
scoringNoOpt-in ranking mode (#55). 'composite' re-ranks chunks by relevance + graph proximity + entity centrality, adding composite_score and score_components fields. Omit for default relevance-only ranking.
max_hopsNoMaximum hops for related-entity discovery
entity_idYesCanonical entity id (slug) returned by memory_explore
include_relatedNoInclude related entities discovered via graph traversal

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description's "Read-only" is consistent with that. Beyond the annotations it discloses the return payload (entity_id, name, ranked chunks, related_entities) and that related-entity discovery is gated by include_related/max_hops — useful behavior for a tool with no output schema. It loses a point for leaking internal roadmap noise ("once #55 lands"), which is not actionable to an agent.

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?

Well structured and front-loaded: one-line purpose, then USE THIS WHEN, Returns, and Examples, each earning its place. The only wasted text is the internal ticket reference "#55" appearing twice, which adds no value for a caller.

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 6-parameter read tool with no output schema, the description covers what the call returns, when to reach for it, and worked examples, which is enough to invoke it correctly. Minor gaps remain around how ranked chunks are ordered by default and what happens when entity_id is not found, but nothing essential is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, and the description adds a little: the Returns section explains that include_related and max_hops actually control whether neighbours appear, and the three examples show realistic parameter combinations including disabling related entities and expanding hops. It stops short of explaining limit/scoring trade-offs beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: "Get the full ranked detail for a single entity," and the Returns section clarifies it yields chunks plus related entities. It does not explicitly contrast itself with siblings such as memory_graph or memory_search, so it falls just short of full sibling differentiation, but an agent can tell what it does without opening the schema.

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?

The "USE THIS WHEN" block gives two concrete triggers — drilling into one entity from a knowledge map and needing the ranked chunk list plus neighbours. It gives clear context but no explicit exclusions or named alternatives for the case where the user has no canonical entity id yet (only the schema hints that memory_explore produces one).

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