UK Data for Agents

vehicle_crash_ratings

Read-onlyIdempotent

How safe is this car in a crash? Returns the US NCAP 5-Star Safety Ratings for a make, model and model year, one entry per body style or drivetrain: overall, frontal (driver and passenger), side barrier and side pole, and rollover stars with the rollover risk percentage. For family car buyers comparing models. Source: NHTSA NCAP. These are US tests; Euro NCAP scores for UK-market cars are separate and not comparable star for star. (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": "vehicle_crash_ratings"
  }
}

Input Schema

Name	Required	Description
`make`	No	string, required, vehicle make, e.g. honda
`model`	No	string, required, US model name, e.g. accord
`modelYear`	No	integer, required, model year, e.g. 2019

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's value-add is the disclosure that results are one entry per body style or drivetrain (multi-row output from a single call), the exact rating components returned, the authoritative source (NHTSA), and a 1-credit cost. Missing only edge behavior (no-data years, invalid make/model handling), 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?

Front-loaded with the user-facing question, then the payload, then the caveat and cost — good ordering with no redundancy. The 'For family car buyers' audience line and rhetorical opener are slightly promotional rather than operational, costing it a point.

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?

There is no output schema, and the description compensates by enumerating the fields returned and their granularity, plus the credit cost and a comparability caveat. For a three-parameter read-only lookup, nothing an agent needs in order to call it or interpret the response is missing.

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 make/model/modelYear are already documented, including the 'US model name' nuance and the year example. The description adds only that one query can yield several rows across body styles/drivetrains; it adds no format or normalization guidance beyond the schema, so baseline 3 applies.

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?

Names a specific resource (US NCAP 5-Star Safety Ratings) and the exact inputs (make, model, model year), and enumerates the returned crash dimensions: overall, frontal driver/passenger, side barrier, side pole, rollover plus risk percentage. It also distinguishes itself from the adjacent nl_vehicle / Euro NCAP domain, so an agent can separate it from the other vehicle_* siblings without opening a schema.

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?

Supplies a clear usage frame (comparing models for family car buyers) and an explicit scope/exclusion: these are US tests, and Euro NCAP scores for UK-market cars are not comparable star for star. It stops short of naming a sibling to use instead when the request is non-US, so the exclusion is stated but not routed to an alternative.

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

All UK Data for Agents tools Inspect

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

Need Help?