Skip to main content
Glama

find_related

Finds related wiki notes by traversing bidirectional [[id]] links up to a chosen depth using BFS, leveraging explicit note relationships instead of semantic search.

Instructions

Link graph 기반 관련 노트 찾기 (BFS N-depth).

단순 의미 검색과 다르게 wiki의 [[id]] 양방향 link 그래프로 연결된 노트를 찾음. Atomic notes 간의 명시적 관계를 활용.

Args: note_id: 시작 노트 ID depth: 탐색 깊이 (1-3, 기본 1)

Returns: depth별 관련 노트 + in-degree

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": {
      "note_id": "<note_id>"
    },
    "name": "find_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNo
note_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/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 well: it discloses the traversal algorithm (BFS), the graph semantics (bidirectional `[[id]]` links), the depth bound, and that results include in-degree. It never explicitly states the operation is non-mutating or describes failure behavior for a bad note_id, which is the remaining gap.

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?

Front-loaded with the core purpose and mechanism, then a clarifying contrast, then compact Args/Returns blocks. The sentence about leveraging explicit relationships between atomic notes is mildly redundant with the preceding line, but nothing is wasted overall.

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 two-parameter read tool with an existing output schema, the definition covers mechanism, parameter meaning, and the shape of results (related notes per depth plus in-degree). Missing only explicit read-only confirmation and edge-case behavior, which are minor here.

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 it does: `note_id` is defined as the starting note and `depth` is given a meaningful range (1-3) and default that the schema itself does not enforce via min/max. It does not explain what happens when depth exceeds the graph extent, but the core semantics are covered.

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 names a specific verb and resource ('Link graph 기반 관련 노트 찾기') and pins down the mechanism (BFS over the wiki's `[[id]]` bidirectional link graph). It explicitly contrasts itself with semantic search, so an agent can distinguish it from search_wiki 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?

Usage context is clear: reach for this when you want notes connected by explicit `[[id]]` links rather than by semantic similarity, which effectively routes the agent away from search_wiki. It stops short of explicit when-not-to-use cases (e.g. no links present, or wanting full-text matches), so it is not a 5.

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