MCP server for SimplyBook API providing tools for managing bookings, clients, services, providers, statistics, tickets, memberships, coupons, notes, products, subscriptions, payments, and intake forms
SimplyBook MCP exposes 9 tools with moderate-to-good schema coverage but inconsistent description quality and missing error handling guidance. Naming follows verb_noun convention (get_, create_, edit_, delete_) which is strong. However, parameter descriptions lack actionable constraints, output schemas are not documented, and error recovery guidance is absent. The Spanish descriptions suggest this is a localized implementation, but translation to English with LLM-optimized brevity would improve discoverability. Three tools have very detailed parameter schemas (create_booking, get_booking_list, get_client_memberships) with proper type definitions, enums, and validation notes; others are sparse (get_all_bookings_simple has empty input schema). No tool includes documented output schema structure, forcing LLMs to infer return types. Security posture is unclear, credentials are referenced in environment variables but no evidence of vault integration or permission gates. Overall: solid infrastructure but lacks polish for production LLM agents.
Crear una nueva reserva
Crear un nuevo cliente
Eliminar un cliente
Editar un cliente existente
Obtener lista básica de reservas sin filtros
Obtener lista de reservas con filtros avanzados
Obtener detalles de un cliente
Output schemas not documented. No tool includes a documented return type or response structure. LLMs cannot plan downstream calls or extract the correct fields without reverse-engineering from live calls.
get_all_bookings_simple has empty input schema ({}). This tool is undifferentiated from get_booking_list except that it lacks filters. The distinction should be explicit in descriptions and parameter constraints (e.g., upcoming_only, date range filters).
No error handling or recovery guidance. Tools lack descriptions of failure modes (e.g., 'If client_id not found, try search_clients() first') or actionable error messages. Destructive operations (delete_client) have no confirmation or dry-run mechanism.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 55 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 45 | - | v1 |
Obtener lista de membresías de clientes
Obtener lista de clientes
Parameter descriptions lack concrete validation rules. E.g., 'page' and 'on_page' have 'minimum:1' in schema but no description of max bounds, typical default, or pagination behavior (cursor vs offset).
Tool descriptions are in Spanish. Translation to English with LLM-optimized brevity (50-200 chars) would improve discoverability for non-Spanish-speaking agents and align with Arcade baseline conventions.
No permission gates or scope declarations. Tools for create_client, edit_client, delete_client, and create_booking lack any mention of required permissions or access controls. An agent with insufficient privileges would receive a confusing error instead of an upfront permission denial.
create_booking is a complex multi-step operation with 16 optional parameters. No description of what happens if required service/provider/client combinations are invalid, or if date/time constraints are violated (e.g., end_datetime before start_datetime).
get_booking_list description includes a warning about date range limits ('Puede tener límite de rango de fechas') but no explanation of what the limit is, how to work around it, or what error to expect if violated.