Skip to main content
Glama

BRAINIAC Food Hygiene Ratings

Search food businesses

food-safety_search

Search UK food businesses by name, location, postcode, or hygiene rating using the Food Standards Agency Food Hygiene Rating Scheme API. Price $0.05 USDC. POST /api/v1/food-safety/search. Unpaid calls return 402 and do not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "food-safety_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
queryYes
latitudeNo
postcodeNo
longitudeNo
maxDistanceNo
ratingValueNo
businessTypeIdNo
localAuthorityIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add valuable behavior: the $0.05 USDC cost, the POST endpoint, and that unpaid calls return 402 without executing. It omits other consequential traits such as pagination behavior, the default/max result window, and whether distance search needs lat/long together with maxDistance.

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

Conciseness4/5

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

Three sentences, front-loaded with purpose, then pricing/endpoint, then the failure mode. No filler, though the endpoint path and price are less useful to an agent than parameter or result detail would have been.

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

Completeness3/5

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

For a 10-parameter, no-annotation, no-output-schema tool, the description covers purpose and payment but leaves key operational gaps: result shape, pagination defaults, and the semantics of most optional filters. An agent could invoke it for a basic query but would likely mis-guess how to use the geographic and identifier filters.

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?

Ten parameters with 0% schema description coverage means the description must compensate, and it partly does by naming the core searchable facets (name, location, postcode, hygiene rating). However, it adds no meaning for page, limit, maxDistance, businessTypeId, localAuthorityId, or the format expected by ratingValue, leaving half the surface undocumented in both places.

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

Purpose4/5

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

States a specific verb and resource ("Search UK food businesses") plus the data source (FSA Food Hygiene Rating Scheme API) and the searchable facets. It is clearly distinct from siblings like food-safety_business or food-safety_authorities by being a multi-facet search, but it never names an alternative explicitly.

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

Usage Guidelines3/5

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

The listed dimensions (name, location, postcode, hygiene rating) imply when to reach for this tool rather than a single-entity lookup, so usage is inferable. However, there is no explicit when-to-use/when-not guidance and no routing to the sibling tools for authority, ratings, batch, or business-detail lookups.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources