Skip to main content
Glama

Car running costs by registration

car_running_costs
Read-onlyIdempotent

Vehicle tax, MOT and other running-cost facts for a UK-registered vehicle. 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": "car_running_costs"
  }
}

Input Schema

NameRequiredDescriptionDefault
registrationYesUK registration plate

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?

The annotations already declare this as a safe, read-only, idempotent lookup, so the description does not need to restate that. It adds useful context by noting the tool is rate limited and by specifying the categories of facts returned, but it does not explain response format or failure behavior.

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 two short sentences with no wasted wording. The core purpose is front-loaded, and the rate-limit warning is brief and useful.

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 simple one-parameter, read-only lookup with no output schema, the description gives enough scope and a rate-limit warning. It could be strengthened with a little more detail about the returned cost categories or registration format, but the essentials are present.

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?

The input schema has 100% description coverage for the single registration parameter. The description adds no syntax or format details beyond what the schema already provides, so the baseline of 3 is appropriate.

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 resource: vehicle tax, MOT, and other running-cost facts for a UK-registered vehicle. It is clear what the tool returns, though it does not explicitly differentiate itself from similar siblings such as vehicle_tax_estimate or fuel_cost_calculator.

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?

The description implies use when looking up running costs for a known UK registration, but it gives no explicit when-to-use or when-not-to-use guidance. It also does not mention alternatives for tax estimates, MOT checks, or fuel costs.

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