Skip to main content
Glama

National Numbers - Private Number Plates

Transfer requirements

transfer_requirements
Read-only

Given a number plate registration, explain transfer/retention requirements, likely DVLA steps, vehicle eligibility, and timescales.

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

Input Schema

NameRequiredDescriptionDefault
registrationYesA UK vehicle number plate registration (e.g. A 1, S7 EVE, MY51 REG)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a non-mutating read, so the bar is lowered. The description still adds real behavioural context by disclosing that the answer covers eligibility and timescales, and the hedge "likely DVLA steps" honestly signals advisory rather than authoritative output. It does not mention data freshness (e.g. whether DVLA rules are live) or any usage limits.

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

Conciseness5/5

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

A single sentence that front-loads the input contract and then lists the four things returned. Every clause carries information; there is no filler or repetition of the title.

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 one fully-described parameter, a readOnly annotation, and no output schema, the description usefully enumerates the shape of the answer, which is exactly the missing piece. Minor gaps remain around authority of the advice and currency of DVLA rules, but an agent has what it needs to select and call it.

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% and the single `registration` parameter is fully documented in the schema with a pattern and examples. The description only restates that the input is a number plate, adding no format or normalisation guidance beyond what the schema already provides. 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 names a specific verb (explain) and a specific resource (transfer/retention requirements) and enumerates the content produced: DVLA steps, vehicle eligibility, timescales. That is clearly distinct from siblings like format_registration or value_registration. It stops short of explicitly naming a sibling to contrast with, so it sits just below the top of the scale.

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?

"Given a number plate registration" supplies the input precondition and implies the use case (a user asking about moving or retaining a plate). There is no explicit when-not guidance, no mention of what to do instead if the user actually wants formatting, valuation, or availability, and no statement of prerequisites or scope limits.

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