solobooks defines 11 tools with basic schemas and descriptions, but falls short of production quality. All tools have descriptions (10-100 chars, mostly adequate), and input schemas are present with type definitions. However, parameter descriptions are sparse or missing entirely, most params lack guidance on format, constraints, or valid values. Output schemas are undocumented. Error handling is absent. No tool annotations (readOnlyHint/destructiveHint). The naming is clear (verb_noun pattern), but composition issues exist: update_* tools accept both name and ID for clients/projects, forcing LLMs to reason about ambiguous lookups. No pagination support on list_* tools. Overall, this is a functional but incomplete toolkit typical of early-stage MCP servers.
Create a new client with optional initial hourly rate.
Create a project for a client.
Full detail for one client: contact info, payment terms, rate history. Accepts client name or ID.
Get company info (name, address, phone, email). Single-row table.
Get consultant details. Defaults to the primary consultant if no ID given.
List clients with current hourly rate. Returns JSON array.
List projects, optionally filtered by client.
Output schemas completely undocumented. No tool returns a documented schema, LLMs cannot predict response structure or plan downstream calls. E.g., list_clients returns 'JSON array' but field names, types, and pagination info are invisible.
Parameter descriptions missing or trivial on most tools. E.g., update_company has params 'name', 'display_name', 'address', 'phone', 'email' with no descriptions explaining what each controls or format constraints. LLMs cannot infer intent.
Ambiguous parameter types on update_client and get_client_detail: 'client' accepts string|integer (name or ID). LLMs must guess whether to pass 'ACME' or '42'. No guidance on lookup precedence or error handling if both match.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
Update client fields. Accepts name or ID. Rate changes create a new rate row (history preserved).
Update company info fields.
Update consultant fields.
Update project fields.
No pagination on list_clients or list_projects. If a user has 500 clients, the entire list is returned, blowing context window. No limit, offset, or cursor parameters.
No error handling guidance. Tools have no documented error cases, recovery steps, or actionable error messages. E.g., if create_client fails due to duplicate name, the LLM has no guidance on what to do next.