Skip to main content
Glama

ULEZ and clean air zone check

ulez_check
Read-onlyIdempotent

Whether a UK-registered vehicle is compliant with the London ULEZ and other clean air zones. Rate limited.

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": "ulez_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
registrationYesUK registration plate

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?

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description contributes a useful extra trait (rate limited) and scopes the check to UK-registered vehicles. It does not say what the result looks like (a boolean verdict vs. a list of zones/fees) despite having no output schema.

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?

Two short sentences with the purpose front-loaded and no filler. The first sentence is a fragment rather than a full clause, but it remains unambiguous and costs nothing.

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, no-output-schema tool this is close to adequate, but two things an agent would want are missing: what a compliant/non-compliant response contains, and which "other clean air zones" are actually covered. The rate-limit note is raised without any indication of threshold or consequence.

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?

There is a single parameter at 100% schema coverage, so the schema already defines it. The description reinforces the constraint that the plate must be UK-registered, which is mild added meaning rather than new syntax or format guidance.

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 names the check concretely: ULEZ and clean-air-zone compliance for a UK-registered vehicle. An agent can tell this apart from data-lookup siblings like vehicle_history_check. It does not explicitly differentiate itself from the sibling clean_air_zones, which is the one plausible overlap.

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 prerequisites, and no routing to alternatives such as free_vehicle_check or clean_air_zones. Usage is only implied by the stated purpose, leaving the agent to infer which tool answers a compliance question.

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