Skip to main content
Glama
aliasunder

Vault Cortex Obsidian MCP Server

Find Orphans

vault_find_orphans
Read-onlyIdempotent

Find notes with no incoming links from other notes or canvases. Surface orphaned notes to integrate into your knowledge graph, with optional folder exclusions and a result limit.

Instructions

Find notes with no incoming links from other notes or canvases — orphans are disconnected from the knowledge graph and may be forgotten or need linking. A note that only links to itself still counts as an orphan (self-links are ignored).

Example: vault_find_orphans({})

When to use: Vault maintenance — surfacing notes to integrate into the graph. Link an orphan by mentioning it from a relevant note with vault_patch_note. Prefer vault_get_backlinks to check the connectivity of one specific note rather than scanning the whole vault.

Parameters:

  • With exclude_folders omitted, the defaults apply; the daily notes folder among them is re-read on each call: DAILY_NOTES_FOLDER, else .obsidian/daily-notes.json, else "Daily Notes" (also used when that file is unreadable). When that folder is the vault root or blank, no daily folder is excluded.

  • exclude_folders replaces the defaults, it does not add to them — list a default yourself to keep it (vault_get_daily_note's path starts with the daily notes folder whenever the defaults exclude one). Pass [] for no exclusions. Each entry names a whole folder, subfolders included ("Projects" also excludes "Projects/Archive" but not "ProjectsOld/"), ignoring ASCII letter case.

  • limit applies after exclusions and sorting by most recently modified. Nothing in the response signals truncation: exactly limit results may mean more exist, so raise limit to check.

Errors:

  • An empty array means no orphans were found (after exclusions), not an error.

  • "too many excluded folders" — pass a shorter exclude_folders list, then retry.

Returns: JSON array of note metadata (path, title, tags, related, folder, type, created, modified, bytes, leading_callout?, additional_properties?), sorted by most recently modified. bytes is the on-disk file size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 50)
exclude_foldersNoFolder paths to exclude (e.g. Projects; default: the daily notes folder, "Templates", "About Me")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.54.13
    • changedInput schema / properties / exclude_folders / description
      Previous value: -"Folder paths to exclude (e.g. Projects; default: daily notes folder, Templates, \"About Me\")"New value: +"Folder paths to exclude (e.g. Projects; default: the daily notes folder, \"Templates\", \"About Me\")"
  2. Changed1 schema field changedv0.54.9
    • changedInput schema / properties / exclude_folders / description
      Previous value: -"Folders to exclude — replaces the defaults ([\"Daily Notes\",\"Templates\",\"About Me\"]), not merged"New value: +"Folder paths to exclude (e.g. Projects; default: daily notes folder, Templates, \"About Me\")"
  3. Changed4 schema fields changedv0.50.0
    • addedInput schema / properties / limit / default
      Added value: +50
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
  4. Changed1 schema field changedv0.22.1
    • addedInput schema / properties / exclude_folders / items / minLength
      Added value: +1
  5. Changed1 schema field changed
    • changedInput schema / properties / exclude_folders / description
      Previous value: -"Folders to exclude (default: [\"Daily Notes\",\"Templates\",\"About Me\"])"New value: +"Folders to exclude — replaces the defaults ([\"Daily Notes\",\"Templates\",\"About Me\"]), not merged"
  6. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial behavior beyond them: the daily-notes folder resolution chain and its re-reading per call, that exclude_folders replaces rather than extends defaults, that truncation is NOT signaled in the response, and the empty-array-not-an-error semantics. This is exactly the kind of context annotations cannot carry.

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 front-loaded (definition, example, when-to-use, parameters, errors, returns) and every section carries load-bearing content. It is on the long side, and the multi-step daily-notes folder fallback chain is dense prose that could be tightened, but nothing is purely redundant.

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?

With no output schema, the description compensates by documenting the return shape (JSON array with path, title, tags, related, folder, type, created, modified, bytes, optional fields, sorted by modified) and the named error case. An agent has everything needed to call, interpret, and recover from this tool.

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

Parameters5/5

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

Schema coverage is 100%, but the description goes well past it: exclude_folders semantics (replace vs. extend defaults, whole-folder with subfolders included, 'Projects' matches 'Projects/Archive' but not 'ProjectsOld/', ASCII case-insensitive, [] for no exclusions) and limit ordering (applied after exclusions and modified-desc sort, with the ambiguity that exactly limit results may mean more exist).

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 precise verb+resource ('Find notes with no incoming links') and defines the resource-boundary case explicitly: a note that only links to itself still counts as an orphan. This distinguishes it cleanly from vault_get_backlinks and vault_get_outgoing_links, which operate on a single known note.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'When to use' framing (vault maintenance, surfacing notes to integrate into the graph) plus a named alternative with the condition that selects it: 'Prefer vault_get_backlinks to check the connectivity of one specific note rather than scanning the whole vault.' Also tells the agent how to act on results via vault_patch_note.

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