Skip to main content
Glama

Official registers near each address (UK)

find_official_places
Read-onlyIdempotent

What open map data doesn't have, from the official registers. England (the Care Quality Commission's register, our copy, with each place's latest rating and date): A&E departments (NHS hospitals with a full emergency department: CQC rates their urgent and emergency services and critical care; with the A&E's rating and the NHS trust that runs it), urgent care (urgent treatment centres and minor injuries units, including hospitals whose A&E became one), hospitals (NHS or independent), GP practices, care homes, nursing homes, dentists, hospices; and NHS community pharmacies from the NHS's own register (England, Wales, Isle of Man; ODS code and UPRN, on their building where the register gives it). UK (the Food Standards Agency, live): food businesses with their hygiene rating. For up to 500 addresses or points (100 for food): the nearest (mode nearest), how many within a radius (count) or a list (list), straight-line km; or mode at: the registered place AT each address (send the business name as name), e.g. the hygiene rating of each restaurant on a customer list or the CQC rating of each care home, matched by name and postcode and saying how; a row that can't be matched says why and lists what is registered there. Filter by rating (Outstanding, Good, Requires improvement, Inadequate, not rated), NHS or independent, food type, hygiene score. Each place carries its register IDs (CQC location, NHS ODS code, UPRN, FSA FHRS), a link to its official page and its source; CQC covers England and the NHS pharmacy register England and Wales; addresses outside a register are told so. Use find_nearby for everything else (shops, stations, parks).

Input Schema

NameRequiredDescriptionDefault
nNoHow many places to return per record.
nhsNoHospitals: true for NHS only, false for independent only.
kindYes
modeNoat: the registered place at each address itself (send name).nearest
ratingNoCQC ratings to keep, e.g. ["Requires improvement", "Inadequate"]. For A&E, the rating of its urgent and emergency services.
sourceNoInstead of typing rows: { sheet: "<Google Sheets link>", tab?: "Sites" } (shared with the InstaMaps service account, or viewable by anyone with the link), { file: "<Drive link to a CSV or Excel file>" }, or { run: "<run_id from an earlier answer>" }. Columns are found by their headers (id, name, address or its parts, lat/lng); name them if they aren't obvious (id_column, address_column, lat_column, lng_column; from_column and to_column for road distances). Rows with coordinates are used as they are.
recordsNo{id, address} or {id, lat, lng}. Send your own ids to merge results back.
addressesNoOr plain addresses/postcodes, numbered from 1.
food_typeNorestaurant, takeaway, pub, supermarket, shop, hotel, school, caring, mobile or manufacturer.
radius_kmNoHow far to look. Defaults: A&E 60, hospital 30, GP 10, care home 10, pharmacy 5, food 1.
backgroundNoWith source: run as a background job and answer at once with job_id (automatic past 200 rows). Check with get_job; write_to_sheet with the job_id puts the results in the sheet as they finish.
max_hygieneNo
min_hygieneNo
include_specialistNoA&E: also the eye and children's hospitals' emergency departments (left out by default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, open-world safety profile, so the description earns credit for adding provenance and failure behavior: exact register coverage by geography, returned IDs (CQC location, ODS, UPRN, FHRS) plus official page and source, and the rule that an unmatched row 'says why and lists what is registered there.' A useful auth note (sheet must be shared with the service account or link-viewable) is also present, though rate limits are not addressed.

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

Conciseness3/5

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

Content is dense and mostly earns its length given 14 parameters and 10 place kinds, but it is delivered as one sprawling paragraph with deep nested parentheses and run-on sentences, and it opens on an oblique phrase ('What open map data doesn't have') rather than the action. Readability and front-loading suffer even though little is pure filler.

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

Completeness5/5

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

Despite high complexity (14 params, nested `source` object, no output schema), the description covers register coverage, mode behavior, source-input handling, filters, batch limits (500/100), background-job behavior, and the fallback tool. Nothing an agent needs to invoke it correctly is missing.

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 high (~79%) with enums for kind and mode, so the baseline is 3; the description goes further by explaining mode=at semantics ('the registered place AT each address... send the business name as name'), the concrete rating vocabulary accepted by the `rating` filter, and the meaning of the NHS/independent and hygiene filters. This usefully compensates for the undocumented `kind` enum values left bare in 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 the specific resource (official-register places: CQC, NHS pharmacy, FSA food businesses) and the specific verb/scope ('for up to 500 addresses or points... the nearest, how many within a radius, or a list'). It explicitly differentiates from its sibling: 'Use find_nearby for everything else (shops, stations, parks).' An agent can route confidently without opening the schema.

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?

It spells out when to use each mode (nearest/count/list vs. mode=at for match-by-name), when to send the business name, which filters apply (rating, NHS/independent, food type, hygiene score), and the fallback (`find_nearby`). Exclusions and alternative are both explicit, including 'addresses outside a register are told so.'

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