Standalone CLI and MCP server for repo-scoped Markdown notes with git integration
The server defines 4 tools with complete schemas and descriptions. Tool names follow verb_noun convention (note_read, note_list, note_write, note_delete). Descriptions are present and substantive (80-150 chars), explaining what each tool does and when to use it. All parameters have type declarations and descriptions. However, output schemas are not documented, LLMs cannot predict what fields to expect from responses. Error handling guidance is absent. The expectedHash parameter in note_write hints at optimistic concurrency but lacks explanation of failure modes. No enum constraints on parameters. Descriptions could be more explicit about prerequisites and side effects.
Delete a note file from the notes vault, then commit and best-effort push it.
List note files in the notes vault for the current project, optionally filtered by tag or grouped across all projects.
Read the full content and SHA-256 revision of a note file from the notes vault.
Write a note file to the notes vault, then commit and best-effort push it.
Output schemas not documented. LLMs cannot predict response structure (fields, types, pagination). note_list likely returns an array but structure is unclear; note_read returns content and hash but format unspecified.
No error handling guidance. Tools do not document failure modes (file not found, permission denied, git push failed, stale write conflict). LLMs cannot recover from errors without explicit recovery hints.
note_write's expectedHash parameter lacks explanation of conflict resolution. Description says 'reject stale overwrites' but does not explain what error is returned or how to recover (retry with fresh hash, merge, etc.).
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | <=2025-11-25 | v2 |
note_list's 'tag' parameter lacks enum constraint or examples. Free-form string invites hallucinated tag values. Should document valid tags or provide a discovery tool.
note_write and note_delete descriptions do not explicitly state they modify state and commit/push. LLMs need to know these are irreversible and may have side effects (git failures, network delays).