APIVerve

Gas Prices

GasPrices

Read-only

Gas Prices: Gas Prices returns average retail gasoline, diesel and LPG prices from official weekly government surveys for the US, the UK, all 27 EU countries and the EU average. Pass a country, or a US state, region or city, to get the latest week with week-over-week and year-over-year changes, in any currency, per liter or per gallon. (Cost: 2 credits)

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

Input Schema

Name	Required	Description
`area`	No	US only: a state code (CA, CO, FL, MA, MN, NY, OH, TX, WA), a region (eastcoast, midwest, gulfcoast, rockymountain, westcoast and the PADD 1 sub-regions) or a city (losangeles, chicago, houston, newyorkcity and more). Omit for the national average. Requires a paid plan.
`date`	No	Date to look up (YYYY-MM-DD). Returns the survey week in effect on that date. Omit for the latest week.
`unit`	No	Volume unit to price per: liter or gallon. Defaults to the source's unit (gallon for the US, liter elsewhere).
`country`	No	Country to get prices for: US, GB, EU (the EU average) or any EU member code such as DE, FR or PL. Defaults to US. Countries other than US require a paid plan.
`currency`	No	Currency to return prices in, as an ISO code (e.g. USD, EUR, GBP). Defaults to the country's own currency.

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error message, null on success
`status`	No	"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare this a safe, open-world read (readOnlyHint, destructiveHint=false, openWorldHint), so the bar is lower. The description still adds genuine context: the data provenance (official weekly government surveys), the update cadence implied by 'latest week with week-over-week and year-over-year changes', and an explicit cost signal ('2 credits'). It stops short of noting the paid-plan requirement for non-US areas, which lives only in the 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 dense sentences that front-load the resource and coverage, then the call pattern. Minor waste in the redundant 'Gas Prices: Gas Prices' preamble, but otherwise every clause carries information.

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 an output schema present and all parameters fully documented, the description need not describe return values. It covers source, geography, unit/currency flexibility, and cost, which is sufficient for an agent to call it. The only real omission is the non-US paid-plan constraint, which is already stated in the country parameter's schema text.

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 the schema already explains area, date, unit, country and currency in detail. The description reinforces the meaning of country/area granularity and the currency and per-liter-or-per-gallon options, but adds no syntax or edge-case detail beyond what the structured fields already provide, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('returns average retail gasoline, diesel and LPG prices') and scopes it precisely: official weekly government surveys, US/UK/27 EU countries plus EU average. This is clearly distinguishable from near-neighbors like CurrencyRate, CPIInflation or InflationRate, which cover different data.

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 description gives usage-shaped guidance ('Pass a country, or a US state, region or city, to get the latest week'), which implies scoping behavior. However, it never states when to prefer this tool over siblings such as CurrencyConverter or CPIInflation, nor does it flag any exclusions or prerequisites (the paid-plan condition only appears in the schema).

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

All APIVerve tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.