Skip to main content
Glama

get_fuel_prices

Read-onlyIdempotent

Get current fuel prices across Iceland by station.

Returns prices per litre in ISK for each fuel station.
When lat/lon provided: sorted by distance with distance_km field.
Otherwise: sorted by cheapest bensin95 price first.

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_fuel_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAlias for max_results (deprecated, use max_results).
latitudeNoWGS84 latitude to sort stations by proximity.
fuel_typeNoFuel type filter.all
longitudeNoWGS84 longitude to sort stations by proximity.
max_resultsNoMaximum number of stations to return.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral detail beyond that: prices are per litre in ISK, results are distance-sorted with a distance_km field when coordinates are given, otherwise ordered by cheapest bensin95.

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?

Three short lines, front-loaded with the purpose, then the return unit, then the ordering rules — easy to scan with no filler. The 'Returns prices per litre in ISK' line slightly overlaps the existing output schema but still earns its place by conveying currency and unit.

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 a rich annotation set, full schema coverage and an output schema, the description only needs to cover behavior the structured fields cannot: currency/unit and the conditional sort order, both of which it does. Nothing essential to a correct call is missing, though edge cases (invalid coordinates, limit vs max_results interaction) go unmentioned.

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%, so each parameter is already documented, and the baseline is 3. The description adds some meaning by explaining the consequence of supplying lat/lon (distance sorting plus a distance_km field) and the default ordering by cheapest bensin95, but says nothing about fuel_type, max_results, or the deprecated limit alias.

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?

States a specific verb and resource ('Get current fuel prices') plus the geographic scope ('across Iceland') and granularity ('by station'). An agent can immediately tell what it retrieves; no sibling in the list covers fuel, so differentiation is implicit rather than stated.

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?

The conditional sorting rules ('When lat/lon provided... Otherwise...') implicitly tell the agent when to supply coordinates, which is useful. However, there is no explicit when-to-use/when-not guidance and no named alternative for related needs (e.g., price quotes), leaving usage largely inferred.

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