Skip to main content
Glama

BRAINIAC Food Hygiene Ratings

Get food safety authorities

food-safety_authorities

Retrieve the list of local authorities and their establishment counts from the Food Standards Agency Food Hygiene Rating Scheme API. Price $0.02 USDC. POST /api/v1/food-safety/authorities. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "food-safety_authorities"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
regionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

With no annotations supplied, the description does real work: it discloses the cost ($0.02 USDC), the HTTP method and path, and the failure mode (unpaid calls return 402 and do not execute). That is exactly the kind of behavioral context annotations would normally carry. It stops short of describing pagination semantics or result ordering, which keeps it from a 5.

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 short sentences, front-loaded with the purpose, then the commercial and failure-mode facts. The endpoint path is arguably redundant with the tool name but is defensible in a paid API context. No filler sentences.

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 simple three-parameter list endpoint with no output schema, the description covers cost, transport, and failure behavior but leaves the parameters and return shape entirely to the schema and to inference. It is adequate but leaves an agent unsure how to scope a region query or what the establishment counts look like.

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% for all three parameters (page, limit, regionName), so the description must compensate and does not. 'Page' and 'limit' are conventional enough to guess, but regionName — a string filter with a 100-character cap — is never explained, including whether it matches exactly, partially, or covers regions rather than authorities.

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 names a specific verb and resource: 'Retrieve the list of local authorities and their establishment counts', with the upstream source (FSA Food Hygiene Rating Scheme API) identified. That is enough to distinguish it from siblings like food-safety_business or food-safety_ratings, though the description never explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus the sibling tools (search, ratings, business, batch) or when not to. An agent must infer from the resource name alone that this is a directory/aggregate lookup rather than a per-establishment query.

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