Skip to main content
Glama

National Numbers - Private Number Plates

Lookup registration

lookup_registration
Read-only

Given a number plate registration, confirm validity and return the plate format, age identifier, year of issue, region/local office information and notes.

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": "lookup_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

B3.2/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 read, so the description is not carrying the full behavioral burden. It usefully discloses the returned data fields in the absence of an output schema, but says nothing about what happens for an invalid or unrecognized plate (error vs. a validity=false result) or about any rate limits or data-source recency.

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?

It is a single sentence with the input condition front-loaded ('Given a number plate registration') followed by the action and the returned fields, with no filler. The enumeration of five returned attributes is dense but each item earns its place as a substitute for a missing output schema.

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 no output schema, the description does the important work of enumerating what comes back, which is the main gap it needed to fill. The remaining omission is invalid-input behavior, which is minor for a tool this simple and whose safety profile is already covered by annotations.

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 already documents the type, the UK-plate meaning, examples (A 1, S7 EVE, MY51 REG), the character pattern and length bounds. The description only restates 'a number plate registration', adding no normalization, whitespace, or case-handling guidance beyond the schema, so the baseline of 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 set (confirm validity, return plate format, age identifier, year of issue, region, notes) against a specific resource (a UK number plate registration). An agent can tell this is an informational decode/lookup tool, though the phrase 'return the plate format' overlaps semantically with the sibling format_registration and is not explicitly distinguished.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no prerequisites, and no named alternatives among the siblings (format_registration, value_registration, check_availability). Usage is only inferable from the word 'lookup' and the read-only nature of the operation, leaving the agent to guess why it would pick this over the formatting or valuation tools.

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