Skip to main content
Glama

National Numbers - Private Number Plates

Check availability

check_availability
Read-only

Given a number plate registration, confirm validity and return details of its current availability, pricing, and any additional information about the registration.

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

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?

readOnlyHint=true already tells the agent this is a safe, non-mutating call, so the bar is lower. The description adds the useful signal that the response covers availability and pricing, but leaves open what happens on an invalid plate (error vs. a validity flag) and says nothing about rate limits or data freshness.

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 front-loaded sentence with no preamble or repetition. The trailing clause 'any additional information about the registration' is vague filler that slightly dilutes an otherwise tight definition.

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 lookup with a fully documented schema, the description covers the essentials: what it validates and what it returns. With no output schema present, a brief note on the shape of the availability/pricing result would have closed the remaining gap.

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%: the single 'registration' parameter is documented with a pattern, length bounds, and three concrete UK examples. The description only restates 'number plate registration' and adds no format, normalization, or casing 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair (confirm validity, return details) against a specific resource (a number plate registration), and enumerates the payload: availability, pricing, and additional info. That output profile distinguishes it in spirit from siblings like value_registration or format_registration, but the description never names or contrasts 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 this is the tool for asking whether a plate is available and what it costs. There is no statement of when to prefer it over lookup_registration or value_registration, and no prerequisites or exclusions are given.

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