Skip to main content
Glama
Sign In

ThaiData UK

by uk.thaidata
OverviewDiscussionsAdmin

Hygiene profile

get_hygiene_profile
Read-onlyIdempotent

Food hygiene profile for Thai venues in a city, a local authority or a postcode district: the distribution of FHRS ratings 0-5 with mean and counts, or FHIS pass/improvement counts in Scotland, plus how old the inspections are. Use for 'how hygienic are Thai places in X' or 'are these ratings out of date'. Returns counts and dates only - no composite score, and hygiene is not food quality.

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": "get_hygiene_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity or area name.
outcodeNoPostcode district, the part before the space, e.g. 'LS2'. Use instead of city.
local_authorityNoLocal authority name, e.g. 'Leeds'. Use instead of city.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world lookup. The description adds meaningful behavioral context beyond that: it returns counts and dates only, has no composite score, distinguishes FHRS from FHIS coverage in Scotland, and reports inspection age.

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?

The definition is front-loaded with the core purpose, followed by the two supported rating regimes and usage examples. Every sentence carries information about scope, output, or interpretation; there is no filler.

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?

There is no output schema, so the description must explain the return shape, and it does so adequately by describing rating distributions, means, counts, FHIS outcomes and inspection age. It could be slightly more complete on behavior with zero or multiple location parameters, but it is sufficient for this read-only lookup.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema itself explains that outcode and local_authority are alternatives to city. The description reinforces that the profile can be scoped by city, local authority or postcode district, but adds no further parameter syntax or mutual-exclusion detail beyond the schema.

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?

The description names a specific verb and resource, a hygiene profile, and precisises the resource as FHRS rating distributions 0-5 with mean/counts or FHIS pass/improvement counts for Thai venues. It also scopes the geography to a city, local authority or postcode district, so the agent can distinguish it from siblings such as get_city_stats or search_restaurants.

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

Usage Guidelines4/5

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

It gives explicit trigger phrases ('how hygienic are Thai places in X', 'are these ratings out of date') and clarifies that this is not a composite score or a food-quality measure. It does not name a sibling alternative to use instead, which keeps it below a 5.

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

All ThaiData UK toolsInspect
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.

Resources