Skip to main content
Glama

National Numbers - Private Number Plates

Format registration

format_registration
Read-only

Given a number plate registration, correctly space and format it 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": {
      "registration": "<registration>"
    },
    "name": "format_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?

readOnlyHint=true already tells the agent this is a safe, non-mutating operation. The description adds the useful detail that the result is a legally-correctly-spaced string, but says nothing about how invalid or ambiguous input is handled, nor about the return shape (e.g. whether it echoes the input, errors, or normalizes case).

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 no filler; the purpose clause (legal UK road use) comes after the action, which is the right order. Nothing is wasted, though there is also very little substance.

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, fully-described-schema tool with no output schema, the description covers what the tool does and why. The only meaningful gap is guidance on the bulk sibling and on the returned value, both minor at this complexity.

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 schema already gives the pattern, length bounds, and three examples (A 1, S7 EVE, MY51 REG). The description adds no format rules, spacing conventions, or handling of unspaced input beyond what the schema states, so the 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?

The description pairs a specific verb ("space and format") with a specific resource ("number plate registration") and states the purpose (legal UK road use), which clearly separates it from lookup_ or value_-style siblings. It stops short of naming the closest sibling, bulk_format_registration, so the boundary is inferred rather than stated.

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: the singular "a number plate registration" suggests one-at-a-time formatting, and the sibling list contains bulk_format_registration, but the description never says to use that one for multiple plates or when not to use this one. No prerequisites or error conditions are mentioned.

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