Skip to main content
Glama

related_notes

Find notes that share graph entities with a given note, directly or through up to a set number of hops; rank strongest connections first and show the entity chain linking each result.

Instructions

Notes that share graph entities with the given note, directly or through up to hops steps. Strongest connections come first, at most limit results, and each one shows the chain of entities that links it.

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": {
      "path": "<path>"
    },
    "name": "related_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
hopsNo
pathYes
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

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 burden and does a reasonable job: it discloses result ordering (strongest connections first), a hard cap on returned items via limit, and that each result carries its linking entity chain. It omits whether hops increases cost/latency, whether the operation is strictly read-only, and how 'strength' is defined, which are the main behavioral gaps.

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 tight sentences with the core behavior front-loaded and no filler. Minor phrasing friction in 'up to hops steps', but every clause conveys usable information about scope, ordering, capping, and return shape.

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 read-oriented, three-parameter graph query with an existing output schema, the description covers scope, ordering, sizing, and result content adequately. The remaining gap is cost/behavior of larger hops values and the definition of connection strength, both minor against a documented return schema.

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 0%, so the description must compensate and largely does: hops is explained as the traversal depth ('through up to hops steps'), limit as the result cap ('at most limit results'), and path as the anchor note ('the given note'). Only path lacks any format hint (vault-relative vs. absolute).

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 names a concrete verb-and-resource: it returns notes that share graph entities with a given note, traversing up to a bounded number of hops. That is specific enough to distinguish it from a plain backlinks or full-text search tool, though it never names a sibling explicitly to sharpen the contrast.

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?

Usage is implied rather than stated: an agent can infer it should call this when it has a note path and wants semantically/graph-adjacent notes. There is no explicit when-not guidance (e.g., use get_backlinks for direct links, query_notes for exact filters) and no prerequisites are mentioned.

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