UK Food Hygiene MCP — Food Standards Agency food hygiene ratings (FHRS)
Two well-named tools with comprehensive descriptions and complete input schemas. Tool names follow verb_noun pattern (search, details). Descriptions are detailed (200+ chars) and explain use cases clearly. Input schemas include type definitions and parameter descriptions for all fields. However, output schemas are not documented, LLMs cannot predict response structure for downstream chaining. Error handling is present but generic. No tool annotations (readOnlyHint, idempotentHint) despite both tools being read-only. Parameter descriptions are strong but lack explicit constraints (e.g., min_rating range 1-5 is stated but not formalized as enum or min/max).
Get the full Food Standards Agency FHRS inspection record for one UK establishment by its FHRSID (from uk_food_hygiene_search) — rating, inspection date, sub-scores for hygiene / structural compliance / confidence in management (0 = best, higher = worse), full address, local authority contact, and geocode. Use to check how clean or safe a specific UK restaurant, takeaway, cafe, or pub is. Example: uk_food_hygiene_details({ fhrsid: 537122 })
Search UK restaurant food hygiene ratings from the Food Standards Agency FHRS — answers "is this restaurant clean", "is this takeaway safe to eat at", "food hygiene rating of X". Search by business name and/or address (a town, street, or postcode works), or by latitude/longitude + radius_miles for hygiene ratings near a point. Filter by business_type (restaurant, takeaway, pub, hotel, supermarket, mobile caterer...) and min_rating (1-5). Returns rating (0-5 in England/Wales/NI; Scotland uses "Pass"/"Improvement Required" under FHIS), inspection date, address, and inspection sub-scores. Example: uk_food_hygiene_search({ name: "Nandos", address: "Leeds" })
Output schemas not documented. LLMs cannot predict response structure (fields, types, nesting) for downstream tool chaining or data extraction. Breaks the pattern:tool-chain pattern.
No tool annotations despite both tools being read-only. Missing readOnlyHint annotation prevents agents from understanding safety profile and optimizing retry/caching strategies.
Parameter constraints stated in descriptions but not formalized. min_rating '1-5' and radius_miles 'max 30' are prose; should be JSON Schema min/max or enum. LLMs cannot parse prose constraints reliably.
Error messages are generic ('not found', 'API error'). Do not guide LLM recovery. Should include actionable next steps: 'Try search_users() with partial name' or 'Verify fhrsid from uk_food_hygiene_search'.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
No pagination support in uk_food_hygiene_search. If search returns >10 results (default limit), no mechanism to fetch next page. Large result sets risk context window exhaustion.