Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_german_license_plate_info

Decode 700+ German vehicle license plate prefixes (Kfz-Kennzeichen & Altkennzeichen like CLZ, WAN, M, B) and telephone area codes (Vorwahlen).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_german_license_plate_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
plate_or_cityNoLicense plate code (e.g. CLZ, HH, M), city name, or area code (e.g. 030, 089)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose meaningful scope: 700+ prefixes, inclusion of legacy Altkennzeichen, and coverage of telephone area codes. It still says nothing about what the response contains (city, state, region?), whether lookups are case-insensitive, or how ambiguous inputs are handled.

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 filler: verb first, scope and examples after. It is efficient, though splicing plate decoding and area-code lookup into a single clause makes the dual function slightly dense.

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 one-parameter lookup with no output schema and no annotations, the description covers the input universe adequately but omits return-value expectations and ambiguity handling. An agent knows what to send but not exactly what it will get back.

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 property already documents accepted forms with examples (CLZ, HH, M, 030, 089). The description restates the same categories without adding parsing rules, case sensitivity, or ambiguity behavior, 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 ("Decode") with a specific resource (German license plate prefixes / Kfz-Kennzeichen, Altkennzeichen, and Vorwahlen) and gives concrete examples (CLZ, WAN, M, B). This leaves no doubt about what the tool does, though there is no sibling to distinguish it from since the other listed tools are unrelated German utility services.

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 examples of plate codes, city names, and area codes suggest when the tool is applicable, but there is no explicit statement of when to use it, when not to, or how to choose between plate lookup versus city lookup. No alternative tools exist among the siblings, so the omission is low-cost.

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