FastMCP server exposing an Obsidian vault from the filesystem with semantic search, wikilink management, tag taxonomy, and graph health inspection
28 tools with consistent naming (verb_noun pattern) and descriptions present. However, parameter descriptions are minimal (often single-phrase), output schemas are not documented in the source, and error handling guidance is absent. Tool names are clear and action-oriented, but descriptions lack the 50-200 char LLM-optimized range (most are 20-50 chars). No evidence of input validation rules, constraints, or recovery guidance in descriptions. Schemas visible for inputs but outputs undocumented.
Add a wikilink from one note to another (idempotent)
Create a daily note for a specific date
Create a new note from a template
Find semantically duplicate or near-duplicate notes
Find notes that could be linked based on text matching
Find notes with no incoming or outgoing links
Find notes semantically similar to a given note
Output schemas not documented. No evidence of return type definitions for any of the 28 tools. LLMs cannot plan downstream calls or extract required fields without knowing what each tool returns.
Parameter descriptions are minimal (10-30 chars) and lack actionable constraints. E.g., 'search_simple' query param has no guidance on exact vs partial matching, regex support, or case sensitivity. 'semantic_search' k param lacks range (1-100? 1-1000?).
No error handling guidance in tool descriptions. Destructive tools (vault_delete, move_note) lack confirmation/dry-run patterns or recovery instructions. No guidance on what to do if a path doesn't exist or a wikilink is already present.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 63 | <=2025-11-25 | v2 |
Find wikilinks that point to non-existent notes
Get the YAML frontmatter of a note
List all notes that link to a given note
List all wikilinks from a note
List recently modified notes
List all tags in the vault with usage counts
Merge one tag into another across all notes
Move or rename a note and rewrite all backlinks
Remove a wikilink from a note
Rename a tag across all notes
Search for exact strings in note content
Search for notes by semantic meaning using embeddings
Create a restore point (snapshot) of the vault state
Undo the most recent batch of edits (restore from last snapshot)
Create or update a template note
Append content to an existing note
Delete a note from the vault
Read a note from the vault
Set or update YAML frontmatter on a note
Get statistics about the vault (note count, tag count, etc.)
Write or overwrite a note in the vault
Tool descriptions lack context on when to use similar tools. E.g., search_simple vs semantic_search distinction is not explained in either description. LLMs must guess which to call for a given query.
No pagination or result-limiting guidance. Tools like list_tags, vault_stats, find_orphans do not document max result counts or pagination support. Large vaults could return thousands of items, exhausting context.