Vault MCP server for Limbo — exposes vault_search, vault_read, vault_write_note, vault_update_map
16 tools with mixed quality. Naming is verb-forward and clear (vault_search, calendar_create, cron_add). Descriptions are present but often generic, many lack actionable context for LLM selection. Schemas are visible and typed, but parameter descriptions are sparse or missing. No output schemas documented. Error handling and recovery guidance absent. Security concerns: workspace_write and vault_store_file accept arbitrary paths without validation hints; no mention of permission gates or audit trails. Composition is reasonable (separate read/write tools), but tools like vault_store_file combine file storage + note creation, violating single-responsibility. STDIO transport caps protocol readiness at 50.
Create a new event on Google Calendar.
Delete an event from Google Calendar by event ID.
Read Google Calendar events for a specified date range. Returns event details including title, time, attendees, and description.
Update an existing event on Google Calendar.
Add a new scheduled cron job.
List all scheduled cron jobs.
Remove a scheduled cron job by ID.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., what does vault_search return? Is it a list of objects with title/snippet/domain fields?). Breaks tool chaining.
workspace_write and vault_store_file accept arbitrary file paths without validation hints or security warnings. No mention of path traversal guards, permission checks, or audit logging. LLMs could be tricked into writing to sensitive locations.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | <=2025-11-25 | v2 |
Trigger an update check and optionally install a new version of Limbo.
Retrieve a stored file by its linked note ID. Reads the note's asset_path from frontmatter and returns metadata plus an absolute path reference so Telegram responses can send it as a real attachment.
Read the full content of a vault note by ID. Searches recursively through subdirectories. Returns raw markdown including YAML frontmatter.
Search notes in the vault by keyword query. Recursively searches all subdirectories. Returns matching notes with titles, snippets, relevance scores, and domain (subdirectory).
Store a file (image, PDF, document) in the vault and create a linked note. Preferred: pass filePath to copy a local file (e.g. from telegram_files/). Fallback: pass filename + fileData as base64. The source file is deleted after a successful copy.
Append entries to a section in a Map of Content (MOC). Creates the map file (with frontmatter) and/or section if they don't exist. Maps live in vault/maps/.
Create or overwrite a vault note with YAML frontmatter. Supports subdirectory organization — creates the subdirectory if it doesn't exist.
Read a file from the OpenClaw workspace (e.g. workspace/skills/, workspace/system/). Returns raw file content.
Write or overwrite a file in the OpenClaw workspace. Creates parent directories if needed.
Destructive tools (calendar_delete, cron_remove) lack confirmation/dry-run patterns. No guidance on recovery or undo. LLMs may delete events or jobs without user consent.
Parameter descriptions are sparse or generic. E.g., vault_write_note 'subdirectory' param lacks format/constraint hints; calendar_read 'startDate'/'endDate' lack examples or validation rules; cron_add 'schedule' lacks cron syntax guidance. LLMs will guess at valid formats.
vault_store_file combines file storage + note creation (two concerns). Should split into separate tools so agents can compose them independently. Violates single-responsibility principle.