Skip to main content
Glama

Flow Diesel Prices: diesel prices near a point

diesel_prices_near

Flow Diesel Prices. Returns posted retail diesel prices at truck stops near a point, nearest first, from ValveRide Flow's price data. The result is { data: StationPrice[] }; stations with no price to offer are left out. 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. radius is in miles (default 10, max 50); limit defaults to 50 (max 100). 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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "diesel_prices_near"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude, -90 to 90
lonYesLongitude, -180 to 180 (lng is accepted too)
limitNoMaximum stations returned, 1 to 100
radiusNoSearch radius in miles, up to 50
include_estimatedNoInclude modeled estimates for stations with 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.1/5.0
Behavior4/5

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

Beyond annotations, it discloses that stations without a price are omitted, that prices are pump-posted before discounts, that 'estimated' means modeled from nearby observations, and that the call counts toward the key's plan — meaningful metering/billing context. The readOnlyHint=false annotation is not contradicted, since the description explains the plan-usage side effect of the lookup.

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?

Purpose is front-loaded in the first sentence, and the remaining content is dense but mostly load-bearing (return shape, defaults, auth). The output-field enumeration makes it long, though with no output schema that detail is necessary rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 fully specifies the return envelope and field meanings, plus defaults, limits, auth requirements, and omission behavior. An agent has everything needed to invoke and interpret the result, with only sibling differentiation left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, yet the description still adds real meaning: radius default 10 and max 50, limit default 50 and max 100, and the pricing semantics (USD per gallon, pre-discount) plus confidence/estimated field interpretation. This goes clearly beyond the terse schema property descriptions.

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 first sentence gives a specific verb and resource: 'Returns posted retail diesel prices at truck stops near a point, nearest first,' and names the data source. It does not explicitly distinguish itself from siblings like diesel_price_station (single-station lookup) or fuel_market_snapshot, so an agent must infer the difference from the 'near a point' geography.

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 by 'near a point' and the radius semantics; there is no explicit statement of when to prefer this over diesel_price_station or fuel_market_snapshot. The auth/billing guidance (partner key vs developer key) is clear, but selection guidance against alternatives is absent.

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