Skip to main content
Glama

UK Road Collisions: Collisions in a local authority

uk-road-safety__local-authority
Read-onlyIdempotent

Five-year (or one-year) collision totals for a local authority district by severity and year, road class, speed limit, light, weather, surface and urban/rural. A few free samples a day, then $0.003 USDC per call via x402.

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": {
      "code": "<code>"
    },
    "name": "uk-road-safety__local-authority"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesONS local authority district code
yearNoOne year only

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safe-read profile (readOnlyHint, idempotentHint, non-destructive), so the description's main added value is the pricing/rate-limit disclosure ('a few free samples a day, then $0.003 USDC per call via x402'), which is genuinely useful behavioral context an agent cannot get from the schema. It does not state what happens when results exceed pagination limits, but for a read-only aggregate call the disclosure bar is met.

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?

A single sentence enumerates the output dimensions first and the pricing model last, which is well front-loaded. It is dense but not padded; nothing here is filler, though the pricing clause could arguably live in tool metadata rather than the description.

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?

With a fully documented schema and an output schema present, the description only needs to cover scope, defaults, and cost. The five-year-default behavior is covered and output values need not be explained. The missing piece is routing guidance among the four sibling collision tools.

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%, so both parameters (code = ONS local authority district code, year = one year only) are already documented. The description adds the useful semantic that the year parameter is optional and that omitting it produces a five-year total rather than an error, but adds no format or syntax detail beyond that.

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?

States a specific verb-implied resource (collision totals for a local authority district) and enumerates the dimensions of aggregation (severity, year, road class, speed limit, light, weather, surface, urban/rural). An agent can immediately tell this is an aggregate query over a district, distinct from the point/collision-level siblings.

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?

The description gives no explicit when-to-use guidance and never mentions the sibling tools uk-road-safety__collision, __lsoa, or __near, which is exactly where guidance is most needed given four tools over the same dataset. The only decision-relevant hint is the 'five-year (or one-year)' phrasing, which implicitly signals the time-scope tradeoff.

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