Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Check License Plate

check_license_plate

Look up vehicle data by country code and license plate, returning car, bike, insurance, or MOT details for supported countries.

Instructions

Retrieve vehicle data for a supported country and plate.

Available combinations: IT-car, IT-bike, IT-insurance, FR-car, FR-bike, UK-car, UK-bike, UK-mot, PT-car, PT-insurance, ES-car, ES-bike.

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": {
      "countryCode": "<countryCode>",
      "type": "<type>",
      "licensePlate": "<licensePlate>"
    },
    "name": "check_license_plate"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesrequired, type of information needed (car|bike|insurance|mot)
countryCodeYesrequired, 2 digit country code (IT|FR|UK|DE|PT|ES)
licensePlateYesrequired, the license plate to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description still communicates that this is a retrieval lookup and discloses supported combinations. It does not cover error behavior, permissions, rate limits, or what happens with unsupported inputs, leaving meaningful gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: a purpose sentence followed by a clean list of valid combinations. There is no filler or redundant wording.

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 lookup with full parameter schema coverage, the purpose and valid combinations are sufficient to invoke the tool. Because there is no output schema, however, the description should say more about what vehicle data is returned or how unsupported inputs are handled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all three parameters are already documented. The description adds cross-parameter meaning by listing exactly which countryCode/type pairs are supported, which is useful beyond the schema and clarifies unsupported combinations.

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 states a specific verb ('Retrieve') and resource ('vehicle data') scoped to a supported country and plate. The purpose is clear, but it does not explicitly name or contrast with a sibling tool, so it falls short of a 5.

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?

It lists valid country/type combinations, which gives useful context for supported usage. However, it provides no explicit when-to-use/when-not guidance or alternative for unsupported combinations, so usage is mostly implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.