apibase

UK FSA Food Business Search

ukfsa.establishments.search

Read-onlyIdempotent

Search UK food businesses by name, address, postcode, or local authority. Returns the official Food Hygiene Rating Scheme score (0-5), business type, last inspection date, and full address. Covers 500K+ premises across England, Wales, Northern Ireland (Scotland has separate FHIS — pass/improvement required).

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Business name fragment to search (e.g. 'Tesco', 'Pret', 'Wagamama'). Partial match supported.
`address`	No	Address or postcode fragment (e.g. 'SW1A 1AA', 'Manchester', 'Oxford Street').
`latitude`	No	WGS84 latitude for location-based search (use with longitude + max_distance_miles).
`longitude`	No	WGS84 longitude for location-based search.
`page_size`	No	Results per page (1-50, default 20).
`page_number`	No	Page number for pagination (1-200, default 1).
`max_distance_miles`	No	Search radius from lat/lon in miles (0-100, default 5).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No	Present only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
`result`	No	Tool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 22, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only and non-destructive. Description adds valuable context: returns specific fields (hygiene rating, business type, inspection date, address) and geographic coverage (500K+ premises across GB, excluding Scotland).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: purpose, returned data, scope/exception. No redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With output schema indicated, description covers key aspects. Missing brief mention of location-based search (lat/lon + radius) and pagination, but overall sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear descriptions. Description adds high-level search categories (name, address, postcode, local authority) that complement but do not fully detail all parameters like latitude/longitude or pagination.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Search UK food businesses' and specifies search criteria and return fields. It distinguishes from sibling tools like ukfsa.establishments.detail by focusing on search vs. detail retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly mentions searching by name, address, postcode, or local authority. Notes Scotland has separate FHIS system, guiding users to an alternative tool there.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All apibase tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.