Skip to main content
Glama

Flow Diesel Prices: diesel price at a truck stop

diesel_price_station

Flow Diesel Prices. Returns the posted retail diesel price at one truck stop from ValveRide Flow's price data, by the stop's public station id (pf_ followed by 16 hex characters, as returned by diesel_prices_near). The result is { data: StationPrice }, or { data: null } when the station has no price to offer. Each StationPrice has station_id, source, brand, name, city, state, lat, lng, price (pump-posted retail diesel in US dollars per gallon, before any discount), confidence (0 to 1), estimated (true when the price is modeled from nearby observations rather than observed at the station) and observed_at. On a ValveRide partner API key, send partner_tenant_ref (or the X-Partner-Tenant-Ref header) with every call; the lookup counts toward the key's plan. On a developer API key, partner_tenant_ref is not needed and the lookup counts toward the account's Flow Diesel Prices plan.

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": {
      "station_id": "<station_id>"
    },
    "name": "diesel_price_station"
  }
}

Input Schema

NameRequiredDescriptionDefault
station_idYesPublic station id, e.g. pf_0123456789abcdef
include_estimatedNoReturn a modeled estimate when there is no recent observation (default true)
partner_tenant_refNoPartner API keys only, and required there: your opaque id for the tenant this call is made for. Not needed on a developer API key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / partner_tenant_ref / description
      Previous value: -"Your opaque id for the tenant this call is made for"New value: +"Partner API keys only, and required there: your opaque id for the tenant this call is made for. Not needed on a developer API key."
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the exact return shape ({ data: StationPrice } or { data: null }), the meaning of each field including that price is pump-posted retail before discounts and that estimated signals a modeled rather than observed value, and it discloses the billing consequence ('counts toward the key's plan') plus partner auth requirements and the X-Partner-Tenant-Ref header. The billing side effect also explains why readOnlyHint=false is not a contradiction of a price-read operation.

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?

Front-loaded with purpose and id format, then return shape, then auth/billing — a sensible order with no filler. The sentences are long and comma-heavy, which slightly hurts scanability, but 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 no output schema, describing the StationPrice fields is exactly the right compensation, and auth/billing are covered. The only untold piece is how include_estimated interacts with the estimated flag at call time, which the description leaves entirely to the schema.

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 coverage is 100%, so the schema already documents station_id format, include_estimated, and partner_tenant_ref. The description adds little that is new apart from the header-name alternative for partner_tenant_ref and the per-call billing note, and it never mentions include_estimated directly; baseline 3 is appropriate.

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?

States a specific verb and resource: returns the posted retail diesel price for one truck stop, keyed by public station id. It also implicitly distinguishes itself from diesel_prices_near by citing that tool as the source of valid ids, so an agent can route between single-station lookup and nearby search without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is clear from the workflow linkage: use this after diesel_prices_near has produced a pf_ id to fetch one stop's price. It does not explicitly say when NOT to use it (e.g. bulk or region queries should go to diesel_prices_near or fuel_market_snapshot), so it falls short of full alternative routing.

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