Skip to main content
Glama

National Numbers - Private Number Plates

Suggest registrations

suggest_registrations
Read-only

Given a name, word, or initials, intelligently suggests number plates that would make for a good match.

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": {
      "query": "<query>"
    },
    "name": "suggest_registrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA name, word or initials containing only letters, numbers and spaces
sort_byNoField used to order search results. Defaults to relevance.relevance
sort_orderNoDirection used to order search results.descending
max_price_gbpNoOptional ceiling price. Only registrations with asking prices less than this figure will be returned. If omitted, no maximum price limit is applied.
min_price_gbpNoOptional floor price. Only registrations with asking prices greater than this figure will be returned.
available_onlyNoReturn only registrations currently available. Defaults to false if omitted.
registration_typesNoOptional plate formats to restrict matching to. If omitted, matching plates of all formats will be returned.
vehicle_age_referenceNoOptional vehicle-age restriction. Results will only include registrations suitable for a vehicle of this age. Provide the vehicle's current registration, its first registration date (YYYY-MM-DD), or year of registration. When only a year is supplied, later registration releases from that same year will be excluded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered, but the description adds nothing behavioral beyond that: no mention of what results contain (prices, availability), how filters affect output, or that 'suggestions' are ranked by relevance. The word 'intelligently' is unsubstantiated and conveys no actionable behavior.

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?

A single front-loaded sentence with the input condition stated first, which is efficient. Minor waste in the adverb 'intelligently', which is marketing filler rather than specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter search tool with no output schema, the description is thin: it never says what a suggestion result looks like (plate, price, availability) or how sorting and price/type filters shape results. The rich schema compensates on inputs, but the agent is left guessing about outputs and about how this differs from a plain lookup.

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% across all 8 parameters, including the nuanced vehicle_age_reference union and its conservative-year caveat, so the schema carries the parameter burden. The description mentions none of these filters, so it adds no meaning beyond the schema — 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 ('suggests') and resource ('number plates') plus the input basis (a name, word, or initials), which is enough to tell it apart from lookup_registration or check_availability. It stops short of naming a sibling or explicitly scoping what 'suggest' means relative to an exact lookup.

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 by the phrase 'Given a name, word, or initials' — the reader can infer this is the exploratory/discovery tool rather than an exact-plate tool. There is no explicit when-to-use, when-not-to-use, or pointer to lookup_registration or check_availability for other cases.

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