MCP server for iFood — restaurant orders, menu management (Brazil)
Server has 26 tools with explicit schemas and descriptions. Naming is verb-first and clear (list_, get_, create_, update_, delete_, confirm_, dispatch_, acknowledge_). Descriptions are present and contextual (avg ~120 chars), explaining WHAT each tool does and key prerequisites (e.g., 'May 404 briefly right after PLACED, retry with backoff'). However, input schemas are incomplete: most parameters lack type definitions beyond basic strings/numbers. Parameter descriptions are minimal (10-30 chars) and omit constraints, ranges, and format guidance. Output schemas are not documented. Error handling is absent, no recovery guidance, no categorization of retryable vs. fatal errors. Tool annotations (readOnlyHint, destructiveHint, idempotentHint) are present and correctly applied, which is a strength. Composition is good: tools are single-responsibility and chainable (e.g., list_orders → acknowledge_events → get_order). Security concern: no visible input validation or secret injection pattern.
Acknowledge polled events so iFood stops redelivering them. WARNING: endpoint path is best-guess — verify against live iFood docs.
Request cancellation of an order using a code from get_cancellation_reasons. WARNING: request body is best-guess — verify against live iFood docs.
Confirm/accept an order (first transition after PLACED; orders auto-cancel if not confirmed in time).
Temporarily PAUSE a store for a time window (correct pause mechanism, not opening-hours).
RESUME a store by removing an interruption.
Mark a DELIVERY order as dispatched.
Input schemas lack type definitions and constraints. Most parameters are documented as 'type: string' with minimal description. Missing: enum constraints (e.g., delivered_by should be enum), numeric ranges (page, size), format specs (ISO 8601 dates), and length limits. This forces LLMs to guess valid values.
Output schemas are not documented. Tools return text responses but the structure of that text (JSON fields, arrays, pagination) is not specified. LLMs cannot plan downstream calls or extract required IDs without knowing the response format.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |
Get valid cancellation codes for an order at its current state (feed into cancel_order).
Get full detail for one merchant (name, address, operations).
Get merchant availability per operation/sales-channel (open/closed, reasons).
Get a merchant's configured weekly opening hours.
Get full order detail by ID. May 404 briefly right after PLACED — retry with backoff.
List a merchant's catalogs (step 1 of catalog discovery).
List categories in a catalog (use include_items=true to get item IDs).
List active/future store interruptions (temporary pauses).
List items/products/options in a category.
List merchants the token can access (paginated; size default 100).
Poll iFood order events (one GET per ~30s). Returns new events (PLACED/CONFIRMED/...) or none. Each event MUST be passed to acknowledge_events or it is redelivered forever.
List catalog products (paginated; response wrapped in `elements`).
Mark an order ready for pickup (REQUIRED for TAKEOUT/DINE_IN).
Replace a merchant's ENTIRE weekly schedule (days not sent are removed).
Mark an order as in preparation (optional, recommended between confirm and dispatch/pickup).
Update a menu item's price (reais).
Set a menu item AVAILABLE/UNAVAILABLE.
Update a complement/option price (reais).
Set a complement/option AVAILABLE/UNAVAILABLE.
Create or fully replace an item with its products/optionGroups/options (idempotent).
No error handling or recovery guidance. Tools have no documented error cases, retryability, or actionable error messages. E.g., 'May 404 briefly right after PLACED' is mentioned in list_orders but no guidance on how to handle or retry is provided.
Parameter descriptions are too brief (10-30 chars) and lack actionable constraints. E.g., 'Event IDs to acknowledge' does not specify format, max array size, or what happens if an ID is invalid. 'Comma-separated event types' should specify valid types (PLC, CFM, etc.) as an enum.
No input validation or sanitization visible in handler code. Tool handlers accept raw parameters without type coercion, range checks, or injection prevention. This is a security risk if parameters are passed to external APIs without validation.