Skip to main content
Glama

BRAINIAC Food Hygiene Ratings

Batch lookup food businesses

food-safety_batch

Retrieve details for multiple food businesses in a single batch request using the Food Standards Agency Food Hygiene Rating Scheme API. Price $0.15 USDC. POST /api/v1/food-safety/batch. 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": {
      "fsaIds": "<fsaIds>"
    },
    "name": "food-safety_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
fsaIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries behavioral disclosure itself and does so well: it states the price ($0.15 USDC), the HTTP surface (POST /api/v1/food-safety/batch), and the failure mode (unpaid calls return 402 and do not run). It stops short of describing partial-failure handling for invalid IDs, result ordering, or rate limits.

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?

Four short sentences, front-loaded with the purpose before cost, endpoint, and failure mode. The explicit endpoint path adds little for an MCP caller but costs only a phrase, so overall it is tight and well ordered.

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 one-parameter tool with no output schema, the description covers cost and failure adequately but leaves the agent guessing about the shape of returned 'details' (per-ID objects? errors per ID?) and about batching behavior for partially invalid input. That is a real gap for a paid call the agent cannot preview.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for the single parameter and largely does not. It conveys only that multiple businesses are supplied, while leaving unexplained that the values are FSA establishment IDs, the 1–100 item limits, or what happens with unknown IDs.

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?

The description gives a specific verb and resource ('Retrieve details for multiple food businesses') and scopes it as a 'single batch request', which implicitly separates it from the singular food-safety_business lookup. It does not name that sibling explicitly, so differentiation is inferable rather than stated.

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?

Usage is only implied by the word 'multiple' and 'batch' — an agent can infer this is for many IDs at once, but the description never says when to prefer it over food-safety_business or food-safety_search, nor any prerequisite for obtaining fsaIds. Payment and 402 behavior are covered, but selection guidance is not.

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