Skip to main content
Glama
rps321321

obsidian-mcp-pro

by rps321321
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Find Orphan Notes

find_orphans
Read-onlyIdempotent

Identify disconnected notes in an Obsidian vault’s link graph by classifying fully isolated notes, notes without backlinks, and notes without outlinks to surface abandoned or unlinked content.

Instructions

Identify disconnected notes in the vault's link graph, classified into three groups: fully isolated (no links in or out), no-backlinks (nothing links to them), and no-outlinks (they link to nothing). Returns counts per category and an example list per category, capped by maxResults. Use to surface abandoned notes, missing hub pages, or candidates for archiving.

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum total note paths to list across all categories (1-1000, default: 200). Full counts are always reported regardless.
includeOutlinksCheckNoIf true (default), also report notes with no outgoing links; if false, only report fully-isolated notes and notes with no backlinks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv2.0.0
  3. Removedv1.9.0
  4. Addedv0.1.6
  5. Removedv0.1.4
  6. Changed5 schema fields changedv0.1.2
    • changedInput schema / properties / includeOutlinksCheck / description
      Previous value: -"Also check for notes with no outgoing links"New value: +"If true (default), also report notes with no outgoing links; if false, only report fully-isolated notes and notes with no backlinks."
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum results to return"New value: +"Maximum total note paths to list across all categories (1-5000, default: 200). Full counts are always reported regardless."
    • addedInput schema / properties / maxResults / maximum
      Added value: +5000
    • addedInput schema / properties / maxResults / minimum
      Added value: +1
    • changedInput schema / properties / maxResults / type
      Previous value: -"number"New value: +"integer"
  7. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, so the safety profile is covered. The description adds real behavioral context the annotations cannot: the three-way classification scheme and the return shape (counts per category plus capped example lists).

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-loads the core purpose, then the category definitions, then usage guidance, in three tight sentences. Every sentence carries distinct information with no repetition of name or title.

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-only, two-param tool with a fully documented schema, the description covers purpose, categories, return shape, and usage. Minor gap: it does not clarify interaction between includeOutlinksCheck=false and the reported categories beyond the schema text, but nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters are fully described there, including the maxResults cap and the includeOutlinksCheck toggle. The description only echoes the maxResults cap ('capped by maxResults') without new syntax or edge-case detail, so baseline 3 applies.

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 (identify disconnected notes in the link graph) and enumerates the three sub-categories precisely. An agent can distinguish this from get_backlinks, get_outlinks, and find_broken_links without inspecting other schemas.

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?

Explicitly names the use cases: surfacing abandoned notes, missing hub pages, or archiving candidates. However, it never states when to prefer a sibling tool (e.g., get_backlinks for a single note) or any exclusions, leaving routing to inference.

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