Production-oriented independent MCP server for ezBookkeeping HTTP API
Critical failures across all dimensions. All 16 tools lack descriptions entirely (0 chars each). Input schemas present but parameters uniformly lack descriptions (null values). No output schemas documented. Tool names follow verb_noun convention but lack context. No error handling guidance, no security annotations, no idempotency markers. This server is not production-ready for agent use.
ALL 16 tools lack descriptions. LLMs cannot determine when or why to select a tool without a description. This violates the foundational pattern:tool-description requirement.
ALL parameters across all tools have null descriptions.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 33 | 2025-06-18+ | v2 |
No output schemas documented. LLMs cannot plan downstream tool calls or extract required data without knowing what fields to expect. Violates pattern:tool and pattern:response-shaper.
Destructive operations (delete_transaction, batch_update_transactions, manage_* with delete mode) lack confirmation/dry-run support. No error guidance for recovery. Violates pattern:confirmation-request and pattern:recovery-guide.
Generic 'manage_*' tool names (manage_accounts, manage_categories, etc.) are ambiguous. LLMs cannot infer whether these create, update, delete, or reorder. Split into separate tools: create_account, update_account, delete_account, reorder_accounts.