Skip to main content
Glama

National Numbers - Private Number Plates

Bulk format registration

bulk_format_registration
Read-only

Given multiple number plate registrations, correctly space and format them for legal UK road use.

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": {
      "registrations": "<registrations>"
    },
    "name": "bulk_format_registration"
  }
}

Input Schema

NameRequiredDescriptionDefault
registrationsYesA list of UK vehicle number plate registrations

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 this is a non-mutating operation, and the description is consistent with that. It adds useful domain context ('legal UK road use') that tells the agent the output is compliance-formatted spacing, but it does not disclose what happens to a registration that cannot be legally formatted, whether one bad entry fails the whole batch, or what the result looks like.

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 operation and scope, with zero filler. It is efficient, though the same brevity leaves behavioral questions unanswered.

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

Completeness3/5

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

For a simple read-only formatter with one fully-documented parameter and no output schema, the description is roughly proportionate. However, the input pattern accepts any A-Z0-9 string, so partial-failure and invalid-registration behavior is a real ambiguity that the description should have closed.

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 'registrations' array parameter is fully documented with examples and constraints, so the schema carries the burden. The description only confirms the plural/batch nature of the input, adding little beyond the structured field.

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 phrase ('correctly space and format') and a specific resource ('multiple number plate registrations'), and the word 'multiple' implicitly distinguishes it from the singular format_registration sibling. It doesn't name any sibling explicitly, so an agent must infer the bulk-vs-single split from wording alone.

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 mention of when to prefer the singular format_registration, and no stated preconditions or limits (the 1-50 item cap lives only in the schema). The phrase 'Given multiple...' weakly implies bulk usage, but that is inference rather than guidance.

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