Skip to main content
Glama

UK average fuel prices

uk_fuel_prices
Read-onlyIdempotent

Latest UK average petrol and diesel pump prices (pence per litre) from the weekly DESNZ road fuel prices, with weekly change.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 safety needs no restating. The description adds genuine context beyond them: the underlying dataset (DESNZ weekly road fuel prices), the units (pence per litre), the freshness (latest, updated weekly), and that a weekly change value is included.

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?

A single sentence with the core noun phrase front-loaded and every clause adding information: fuel types, units, source, cadence, and the change metric. Nothing is redundant.

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?

With no output schema, the description must convey the return values, and it does so at a summary level (petrol and diesel averages, pence per litre, weekly change). It stops short of stating the exact period covered or whether regional breakdowns exist, which is a small residual gap.

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?

The tool takes no parameters, so the baseline is 4; there is no input for the description to disambiguate. The description instead characterizes the fixed output shape (two fuel types, pence per litre, weekly delta).

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 exact resource (UK average petrol and diesel pump prices), the unit (pence per litre), and the source (weekly DESNZ road fuel prices). It is clearly a national-average lookup rather than a per-vehicle cost calculation, which separates it from siblings like fuel_cost_calculator or car_running_costs, though it never names an alternative explicitly.

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: an agent can infer this is the tool for headline national pump prices, with the calculators handling derived cost questions. There is no explicit when-to-use or when-not-to-use statement and no reference to any sibling.

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