Skip to main content
Glama
bezata

kObsidian MCP

by bezata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Explore Note Connections

links.connections
Read-onlyIdempotent

Find all notes reachable from a seed note via links, with path traces up to a configurable depth, to map the local network in your vault.

Instructions

Explore the graph neighbourhood around a seed note — direct and multi-hop connections up to depth hops (default 2). Returns the set of reachable notes plus the paths that reach them. Higher depth values blow up result size quickly; keep it ≤3 unless you know the graph is sparse. Read-only.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNoTraversal depth (hops). Default 2. Higher values quickly blow up result size.
noteNameYesName or path of the starting note. Basename match is fine.
vaultPathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.5
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed4 schema fields changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / depth / description
      Added value: +"Traversal depth (hops). Default 2. Higher values quickly blow up result size."
    • addedInput schema / properties / noteName / description
      Added value: +"Name or path of the starting note. Basename match is fine."
    • addedOutput schema / description
      Added value: +"Freeform object. The specific shape depends on the tool; see the tool description."
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds valuable behavioral context beyond annotations, including the cost explosion with higher depth values and the precedence rule for vaultPath over the active vault.

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?

Well-structured and front-loaded: the core behaviour and output come first, followed by cost warning and vault semantics. Slight redundancy exists because 'read-only' and 'result size blow-up' repeat annotation/schema information, but overall every sentence earns its place.

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?

Comprehensive given the annotations, schema, and output schema: it explains scope, output shape, depth risk, and vault resolution. It does not discuss failure modes or when to choose a sibling tool, but the provided context is enough for correct invocation.

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 covers noteName and depth reasonably well, but leaves vaultPath undocumented. The description compensates by explaining that vaultPath overrides the active vault, and reinforces depth semantics with a concrete limit recommendation.

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?

States a specific verb and resource: explores the graph neighbourhood around a seed note with direct and multi-hop connections. Clearly distinguishes itself from sibling direct-link tools like links.outgoing and links.backlinks by describing traversal depth and returning reachable notes plus paths.

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?

Provides clear operational context: the active vault is used by default, vaultPath overrides it, and depth should generally stay ≤3 to avoid result blow-up. It does not explicitly name alternatives or say when to prefer this over a sibling tool, but the guidance is sufficient for practical use.

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

Deploy Server

Other Tools