Skip to main content
Glama

memory_related

Retrieve cross-referenced memories from a knowledge graph to enhance context understanding and connections between stored information.

Instructions

Return cross-referenced memories for a given entry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memory_idYes
refreshNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The tool `memory_related` is implemented as an async function in `memora/server.py`, decorated with `@mcp.tool()`. It calls the helper function `_get_related` to retrieve cross-referenced memories.
    async def memory_related(memory_id: int, refresh: bool = False) -> Dict[str, Any]:
        """Return cross-referenced memories for a given entry."""
    
        related = _get_related(memory_id, refresh)
        return {"id": memory_id, "related": related}
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'cross-referenced' hints at the relationship algorithm, the description fails to explain what constitutes a cross-reference, whether this operation is cached, or what the boolean 'refresh' parameter actually triggers (forced recalculation vs. cache hit).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is efficiently worded with no redundancy, but given the lack of annotations and 0% schema coverage, this brevity is inappropriate. The description is under-specified rather than effectively concise, failing to front-load critical usage constraints.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema (reducing the need to describe return values), the description is incomplete due to undocumented parameters and lack of sibling differentiation. For a complex memory system with 30+ tools, the agent needs more context to invoke this correctly.

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

Parameters2/5

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

Given 0% schema description coverage, the description must compensate by documenting both 'memory_id' and 'refresh'. It only vaguely alludes to 'given entry' (presumably memory_id) and completely omits the 'refresh' parameter's semantics, leaving critical parameters undocumented.

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?

The description states a clear action ('Return') and resource ('cross-referenced memories'), and the term 'cross-referenced' effectively distinguishes this tool from siblings like memory_get or memory_list. However, 'given entry' is slightly vague compared to the actual parameter name 'memory_id'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like memory_hybrid_search, memory_clusters, or memory_get. There are no stated prerequisites, exclusions, or workflow context to help an agent select this tool correctly from the 30+ available memory tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agentic-box/memora'

If you have feedback or need assistance with the MCP directory API, please join our Discord server