Skip to main content
Glama

National Numbers - Private Number Plates

Value registration

value_registration
Read-only

Given a number plate registration, estimate its market value based on historical sales and extensive experience, and list comparable registrations offered by National Numbers.

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

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.5/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe, non-mutating call, so the description only needs to add context. It does disclose the basis of the result (historical sales, 'extensive experience') and that comparables are included in the response, but it omits caveats about estimate accuracy, currency, or whether a range versus a point value is returned.

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 sentence, front-loaded with the primary action and the input, then the secondary listing behavior. Slight marketing phrasing ('extensive experience') is filler but does hint at the estimation method, so it is not wasteful enough to penalize heavily.

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?

For a one-parameter, read-only tool with no output schema, the description covers the input, the primary return (an estimated value), and an additional return (comparable listings). Remaining gaps—estimate precision, currency, and handling of invalid plates—are minor for a tool this simple.

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 single parameter is fully documented with a pattern, length bounds, and UK plate examples (A 1, S7 EVE, MY51 REG). The description adds nothing beyond that, which is the expected baseline when the schema carries the burden.

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+resource: estimate the market value of a UK number plate registration, plus a secondary behavior of listing comparable registrations from National Numbers. This implicitly separates it from siblings such as lookup_registration, check_availability, and format_registration, though it never names them explicitly.

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 only implied: an agent can infer it should call this when a user wants a valuation rather than a plain lookup or availability check. There is no explicit when-to-use statement, no exclusions (e.g., 'do not use for unregistered/private plates'), and no routing to alternatives.

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