Skip to main content
Glama

Memory Related

localnest_memory_related
Read-onlyIdempotent

Retrieve connected memory entries by exploring the knowledge graph one hop in both directions from a specified memory ID.

Instructions

Return all memory entries linked to a given memory ID, traversing the knowledge graph one hop in both directions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
response_formatNojson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaNo

Implementation Reference

  • The tool `localnest_memory_related` is registered here, with its handler defined as an asynchronous function calling `memory.getRelated(id)`.
    registerJsonTool(
      ['localnest_memory_related'],
      {
        title: 'Memory Related',
        description: 'Return all memory entries linked to a given memory ID, traversing the knowledge graph one hop in both directions.',
        inputSchema: {
          id: z.string().min(1)
        },
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: false
        }
      },
      async ({ id }) => normalizeRelatedMemoriesResult(await memory.getRelated(id), id)
    );
Behavior4/5

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

Annotations cover the safety profile (readOnly, non-destructive, idempotent). The description adds valuable behavioral context by explaining the traversal logic (bidirectional, one hop), clarifying how 'related' is defined in the knowledge graph context. It does not contradict 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?

The description is a single, efficient sentence with no filler. It front-loads the action ('Return all memory entries') and immediately follows with the specific constraint and mechanism, maximizing information density.

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?

Given the presence of an output schema (handling return value documentation) and comprehensive annotations (covering safety), the description appropriately focuses on the core graph-traversal behavior. It adequately explains the 'one hop' scope, though explicit mention of handling for disconnected nodes would improve completeness.

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?

With 0% schema description coverage, the description partially compensates by referencing 'a given memory ID,' clarifying the purpose of the required 'id' parameter. However, it fails to mention the optional 'response_format' parameter or provide details on ID format, leaving significant semantic gaps.

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 specific action (Return all memory entries), the target resource (memory entries linked to a given ID), and the unique mechanism (traversing the knowledge graph one hop in both directions). This graph-traversal detail effectively distinguishes it from sibling tools like memory_get or memory_list.

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

Usage Guidelines3/5

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

While the description implies this is for exploring relationships via graph traversal (as opposed to direct retrieval), it lacks explicit guidance on when to use this versus siblings like memory_get or memory_recall. It does not state prerequisites or conditions for selection.

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/wmt-mobile/localnest'

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