obsidian-local-mcp

Overview Schema Source Related Servers Discussions Admin

Neighbors

neighbors

Retrieve adjacent nodes for a given ID in a dependency graph, choosing incoming, outgoing, or both directions to trace dependencies and assess impact.

Instructions

One-hop neighbors of a node. direction is 'out', 'in', or 'both'.

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": {
      "id": "<id>"
    },
    "name": "neighbors"
  }
}

Input Schema

Name	Required	Default
`id`	Yes
`vault`	No
`direction`	No	both
`edge_types`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 11, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only clarifies direction values. It says nothing about behavior on a missing id, vault scoping, or whether results are paginated or truncated.

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?

Two tight sentences with the core scope front-loaded and zero filler. It is efficient, though arguably terse to the point of under-specification.

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?

An output schema exists so return values need not be described, but three of four parameters are undocumented and there is no routing guidance among the many graph siblings. For a graph-query tool in a dense sibling set, this leaves real gaps.

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?

Schema description coverage is 0%, so the schema documents no parameters. The description usefully enumerates the direction values ('out', 'in', 'both') that the schema omits, but leaves id, vault, and edge_types entirely unexplained.

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?

States a specific resource and scope: 'one-hop neighbors of a node'. The 'one-hop' qualifier implicitly distinguishes it from transitive siblings like impact_of and path_between, though no sibling is named explicitly.

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?

There is no when-to-use guidance and no mention of alternatives such as path_between or impact_of. The agent must infer from the name that this returns immediate adjacency only.

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