Skip to main content
Glama

related

Fetch connected memories by memory ID or text query to fill incomplete recall and surface backlinks or similar context in Memoria.

Instructions

Fetch memories connected (backlinks/similarity) to one memory. Use when recall context is incomplete or you need related detail. Pass a memory id or a text query.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "related"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoMemory id from recall or project_context
queryNoOr keywords: the closest memory is found first, then its connections are returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.16.1
    • changedInput schema / properties / id / description
      Previous value: -"ID memori hasil recall"New value: +"Memory id from recall or project_context"
    • changedInput schema / properties / query / description
      Previous value: -"Atau kata kunci untuk menemukan memori terdekat lalu ambil yang terhubung"New value: +"Or keywords: the closest memory is found first, then its connections are returned"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that connections come from backlinks and similarity and that a query resolves to the nearest memory before traversing, but it says nothing about result limits, ordering, or what happens when neither id nor query is supplied (zero required params) or when both are.

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 short sentences, front-loaded with the purpose and followed by the usage trigger and parameter hint. There is little waste, though the phrasing is terse enough to leave gaps rather than being padded.

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

Completeness3/5

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

For a two-parameter tool with no annotations and no output schema, the definition covers purpose and the two input paths but leaves the calling edge cases unaddressed: no defaults for the all-optional signature and no hint about result volume. Adequate to invoke, incomplete for confident use.

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 coverage is 100%, so both parameters are already documented, and the description's main addition is the either/or framing ("Pass a memory id or a text query"). That slightly clarifies the intended selection between the two but adds no format or precedence detail beyond the schema's own text.

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?

"Fetch memories connected (backlinks/similarity) to one memory" names a specific verb, resource, and even the connection mechanisms, so the agent knows it is a graph-adjacency lookup rather than a plain read. It stops short of explicitly distinguishing itself from siblings like recall or get_memory, but the resource-plus-relationship framing is distinctive enough.

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?

"Use when recall context is incomplete or you need related detail" gives a concrete trigger condition and implicitly positions recall as the starting point this tool extends. There are no explicit when-not conditions or named alternatives, which keeps it below a 5.

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