Skip to main content
Glama

UK Data: UK trade, property and planning

cqc_location

Read-onlyIdempotent

CQC location details and current ratings by location id. (cost: 1 credit)

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

Input Schema

NameRequiredDescriptionDefault
locationIdNostring, required

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds a genuinely useful operational fact — the 1-credit cost — but says nothing about behavior on an unknown or malformed location id, or whether ratings reflect a snapshot date.

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?

One front-loaded sentence that identifies the resource, the key, and the cost with no filler. It is terse to the point of being clipped, but every element earns its place.

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?

With one parameter and no output schema, the description carries the burden of telling the agent what comes back; 'details and current ratings' gives a rough shape but not enough to plan downstream use. The credit cost is a welcome addition, but the definition remains minimum-viable for a data-lookup tool.

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 coverage is 100%, so the baseline is 3, and the description only echoes the single parameter's role ('by location id'). The schema's own text ('string, required') is thin and inconsistent with required: [], and the description does not clarify the id format or provenance beyond naming it.

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 resource and scope: CQC location details plus current ratings, keyed by location id. An agent can distinguish it from the sibling cqc_search (which presumably finds locations) without opening the schema. It stops short of a full verb phrase like 'Retrieve', but the intent is unambiguous.

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 implied by the 'by location id' phrasing: call this when you already have an id. There is no explicit statement of when not to use it or a pointer to cqc_search for discovering ids, so the agent must infer the search-then-lookup workflow from sibling names alone.

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