Model Context Protocol server for Wave (waveapps.com) — drives invoices, customers, estimates, bills, and receipts via the internal Wave API.
32 tools with consistent naming (verb_noun pattern) and basic descriptions, but critical gaps in schema completeness and parameter documentation. All tools have descriptions (10-50 chars, below the 50-200 char baseline for LLM optimization). Input schemas visible but severely incomplete: most tools lack detailed parameter type info, constraints, and enums. No output schemas documented. Error handling absent. Composition is sound (single responsibility per tool), but parameter descriptions are minimal, forcing LLMs to infer intent. Example: create_invoice has 'items' param described only as 'Line items for the invoice' with no schema for array element structure. update_* and delete_* tools lack parameter documentation beyond IDs. No pagination support on list_* tools despite Wave API likely returning large result sets.
Create a new bill in Wave
Create a new customer in Wave
Create a new estimate in Wave
Create a new invoice in Wave
Create a new product in Wave
Create a new receipt in Wave
Delete a bill
Delete a customer
All update_* and delete_* tools (12 tools) lack parameter descriptions beyond businessId/resourceId. LLMs cannot infer what fields are updatable or what constraints apply.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., what fields does get_invoice return? Does it include customer_id for chaining?).
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | <=2025-11-25 | v2 |
Delete an estimate
Delete an invoice
Delete a product
Delete a receipt
Get details for a specific bill
Get details for a specific Wave business by ID
Get details for a specific customer
Get details for a specific estimate
Get details for a specific invoice
Get details for a specific product
Get details for a specific receipt
List bills for a Wave business
List Wave businesses/workspaces accessible to the authenticated user
List customers for a Wave business
List estimates for a Wave business
List invoices for a Wave business
List products for a Wave business
List receipts for a Wave business
Update an existing bill
Update an existing customer
Update an existing estimate
Update an existing invoice
Update an existing product
Update an existing receipt
All list_* tools (8 tools) lack pagination parameters (limit, offset/cursor). Wave API likely returns large result sets; missing pagination will blow context windows and force agents to retry with artificial limits.
Complex parameters (e.g., 'items' array in create_invoice) lack schema definition. No element type, required fields, or constraints documented. LLMs will guess structure and fail.
No error handling guidance. Tools do not document what errors are retryable, what user-fixable errors look like, or how to recover. LLMs will not know whether to retry, ask the user, or give up.