Skip to main content
Glama

Detailed vehicle specifications

get_vehicle_details
Read-onlyIdempotent

UK-registered vehicles only. Get a live, non-cached vehicle details lookup for a registration, including vehicle identity and image, body and seating, dimensions, weight and capacity, performance, fuel economy and emissions, EV battery and range, engine, transmission and drivetrain, tyres/tires, brakes and handling, safety and equipment, and available valuation figures and date. Always use this tool for any question about a specific vehicle specification or valuation, even a single field. Only report values returned; null fields are unavailable for that vehicle and must not be guessed. The valuation object may include valuation_url. The live lookup is rate-limited; if unavailable, explain that and do not retry repeatedly.

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": {
      "registration": "<registration>"
    },
    "name": "get_vehicle_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
registrationYesUK vehicle registration (number plate, reg), e.g. WR25 VUP or AB21 XYZ. People usually type it in lowercase without a space, such as wr25vup, and that is still a registration: pass it as given, spaces and case do not matter. Great Britain or Northern Ireland only; plates from other countries will not be found.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, open-world), the description discloses that the lookup is live and non-cached, that it is rate-limited with explicit failure behavior ('explain that and do not retry repeatedly'), and an output-discipline rule (null means unavailable, never guess). That is substantive operational context an agent cannot get from the structured fields.

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?

Scope and the core verb are front-loaded, and the constraint/handling sentences are tight and actionable. The long middle enumeration of data categories is useful for retrieval but bloats the paragraph and could be tightened.

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?

With only one parameter and no output schema, the description carries the burden of describing return content, which it does by enumerating the returned domains and flagging the valuation_url field and the meaning of nulls. An agent has everything needed to call it and interpret results.

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% and the schema already documents the registration format, case/space tolerance, and GB/NI-only constraint. The description repeats the UK-only boundary but adds no new syntax or format meaning, so the baseline 3 applies.

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 opens with a scope restriction (UK-registered only) and a specific verb+resource ('live, non-cached vehicle details lookup for a registration'), then enumerates the returned domains. It does not name any sibling (lookup_vehicle, get_mot_history) to contrast with, so the differentiation is implied by 'Always use this tool for any question about a specific vehicle specification or valuation' rather than stated.

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 a strong positive trigger ('always use this tool for any question about a specific vehicle specification or valuation, even a single field') and an exclusion ('UK-registered vehicles only ... plates from other countries will not be found'). It stops short of naming the alternative tool to use instead when the request falls outside that scope.

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