Turn your Obsidian vault into an active knowledge partner. Dual-loop semantic search with graph-augmented relevance scoring, an interactive semantic galaxy view, and an AI gardener that keeps your notes organized. Supports Google Gemini, Ollama, Voyage AI, and local embedding models, with Model Context Protocol (MCP) tool integration.
12 tools with mostly complete schemas and descriptions, but significant gaps in parameter documentation and error handling guidance. Tool names follow verb_noun convention well (vault_search, read_url, create_note). Descriptions average ~80 chars, below the 194-char baseline for A+ tools. Most parameters lack detailed constraints (ranges, formats, enums). No output schemas documented. Error handling is absent, tools do not guide LLM recovery. Composition is reasonable (single responsibility per tool), but missing idempotency guarantees and chaining metadata.
Use this tool to solve math problems, perform complex logic, or analyze data using code execution.
Create a new folder path recursively.
Create a new note in the vault. Will create parent folders recursively if they don't exist.
Find notes linked to or from a specific note. Use this to discover context not immediately visible in search results.
Perform a Google search to find the latest real-world information, facts, dates, or news.
List the contents of a folder.
List all available external resources provided by connected MCP servers (e.g., files, database schemas, etc.). Use this to discover what resources you can read.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields. create_note, update_note, rename_note, and others return unspecified structures.
Parameter descriptions lack constraints. 'query' in vault_search and google_search have no length limits, format hints, or examples. 'path' parameters lack validation rules (allowed characters, max length). LLMs will pass invalid values.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | <=2025-11-25 | v2 |
Read the full raw content of a note. Use this if you need to refactor or see the complete text of a file.
Read the content of a specific external URL.
Rename or move a note. Updates all internal links automatically.
Update an existing note in the vault.
Search the user's personal Obsidian notes (vault) for information and context.
No error handling guidance. Tools do not document what errors are possible, whether they are retryable, or what the LLM should do next. E.g., read_url may fail on network timeout, 404, or invalid URL, no recovery hints provided.
Destructive tools (create_note, update_note, rename_note, create_folder) lack confirmation or dry-run support. update_note with mode='overwrite' can silently destroy vault content. ToolConfirmationModal exists in UI but is not reflected in tool definitions.
list_folder and list_mcp_resources lack pagination parameters (limit, offset, cursor). Large folders or many MCP resources will return unbounded results, exhausting context window.