Skip to main content
Glama
adrienthebo
by adrienthebo

find_orphaned_notes_tool

Identify and locate notes in your Obsidian vault that lack connections, tags, or metadata to help with organization and cleanup.

Instructions

Find orphaned notes that may need organization or cleanup.

When to use:

  • Regular vault maintenance and cleanup

  • Finding forgotten or disconnected notes

  • Identifying notes that need better organization

  • Preparing for vault reorganization

  • Finding candidates for archival or deletion

Orphan types explained:

  • no_backlinks: Notes with no incoming links (most common definition)

  • no_links: Notes with no incoming OR outgoing links (completely isolated)

  • no_tags: Notes without any tags (untagged content)

  • no_metadata: Notes with minimal/no frontmatter properties

  • isolated: Notes with no links AND no tags (truly disconnected)

Default exclusions:

  • Templates folder (usually contains reference notes)

  • Archive folder (already organized)

  • Daily folder (daily notes often standalone)

When NOT to use:

  • Finding specific notes (use search_notes)

  • Getting all notes in a folder (use list_notes)

  • Finding notes by content (use search tools)

Performance note:

  • Scans entire vault and checks links/metadata for each note

  • For vaults >1000 notes, this may take 10-30 seconds

Returns: List of orphaned notes with paths, reasons, and metadata. Results are sorted by modification date (oldest first).

Example response: { "count": 23, "orphaned_notes": [ { "path": "Random Thoughts/Old Idea.md", "reason": "No incoming links", "modified": "2023-06-15T10:30:00Z", "size": 245, "word_count": 42 } ], "stats": { "total_notes_scanned": 500, "excluded_folders": ["Templates", "Archive", "Daily"], "orphan_type": "no_backlinks" } }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orphan_typeNoWhat makes a note 'orphaned'. Choose the criteria that best fits your organization needs.no_backlinks
exclude_foldersNo
min_age_daysNo
ctxNo
Behavior4/5

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

With no annotations provided, the description carries the full burden and does so well. It discloses performance characteristics ('Scans entire vault', 'may take 10-30 seconds for vaults >1000 notes'), default exclusions (e.g., 'Templates folder'), and what the tool returns (list of notes with metadata). It doesn't contradict any annotations.

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 well-structured with clear sections (e.g., 'When to use', 'Orphan types explained', 'Performance note'), front-loaded key information, and every sentence adds value without redundancy. It's appropriately sized for the tool's complexity.

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?

Given the tool's complexity (4 parameters, no annotations, no output schema), the description is highly complete. It covers purpose, usage, parameters, behavior, performance, exclusions, and includes an example response, providing all necessary context for an agent to use it effectively.

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 description coverage is low (25%), but the description compensates by explaining 'orphan types' in detail (e.g., 'no_backlinks: Notes with no incoming links'), clarifying 'default exclusions' (e.g., 'Templates folder'), and mentioning 'min_age_days' context ('Helps exclude recent work-in-progress'). It adds meaningful context beyond the schema.

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 clearly states the tool's purpose with specific verb ('Find') and resource ('orphaned notes'), and distinguishes it from siblings by explaining what makes notes 'orphaned' (e.g., 'no_backlinks', 'no_links'). It explicitly differentiates from tools like 'search_notes' and 'list_notes'.

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?

The description provides explicit guidance on when to use (e.g., 'Regular vault maintenance and cleanup', 'Finding forgotten or disconnected notes') and when NOT to use (e.g., 'Finding specific notes (use search_notes)', 'Getting all notes in a folder (use list_notes)'), including clear alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adrienthebo/obsidian-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server