Skip to main content
Glama
bezata

kObsidian MCP

by bezata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Find Orphaned Notes

links.orphaned
Read-onlyIdempotent

Find notes with zero incoming and zero outgoing links, disconnected from the vault graph. Use for cleanup and vault-health checks.

Instructions

Return every note with zero incoming AND zero outgoing links — i.e., notes that are disconnected from the rest of the vault graph. Useful for cleanup passes. Read-only. Often paired with links.hubs and links.broken in a weekly vault-health routine.

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
vaultPathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesList of result items; per-item shape depends on the tool.
totalYesNumber of items in `items`.

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. Changed5 schema fields changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedOutput schema / description
      Added value: +"Standard list envelope used by list/search tools."
    • addedOutput schema / properties / items / description
      Added value: +"List of result items; per-item shape depends on the tool."
    • addedOutput schema / properties / items / items / description
      Added value: +"Freeform object. The specific shape depends on the tool; see the tool description."
    • addedOutput schema / properties / total / description
      Added value: +"Number of items in `items`."
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds non-obvious behavioral context: it operates on the session-active vault unless an explicit vaultPath argument overrides it, with the override always winning. This is valuable information beyond the annotations. It doesn't describe return format, but an output schema exists to cover that.

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?

The description is compact and well-structured. The first sentence states the core definition, followed by usage context, then the important vault-selection behavior. No unnecessary filler; every sentence contributes to understanding. The structure is logical and front-loaded with the primary purpose.

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

Completeness5/5

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

For a simple, read-only tool with one optional parameter and an output schema, the description covers everything an agent needs: the exact condition, usage context, and vault selection behavior. It doesn't explain the output structure, but the output schema handles that. The description is complete 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?

The schema has 0% coverage for parameter descriptions, so the description is the only explanation. It clearly explains the optional vaultPath parameter: it overrides the session-active vault and always wins. This gives semantic meaning beyond the raw schema, though it doesn't specify the format (e.g., path syntax), which is a minor gap given there's only one parameter.

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 precisely defines the tool's action: 'Return every note with zero incoming AND zero outgoing links' and explains what that means ('disconnected from the rest of the vault graph'). It clearly distinguishes from sibling tools like links.broken and links.hubs by specifying the dual-direction condition, making the purpose unambiguous.

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?

It provides clear usage contexts: 'useful for cleanup passes' and 'often paired with links.hubs and links.broken in a weekly vault-health routine.' This gives an agent a good sense of when to invoke it. It doesn't explicitly state when not to use it, but the defined scope and pairing guidance are sufficient for typical scenarios.

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