Skip to main content
Glama

US diesel market snapshot (free)

fuel_market_snapshot
Read-onlyIdempotent

Cached US diesel market snapshot from ValveRide Flow's retail price grid, refreshed every 12 hours. Returns national median/p10/p90 retail diesel and per-state percentiles for any states mentioned in origin/destination, plus typical optimized-savings context. Use this for market questions or cost estimates; use optimize_fuel_plan (Flow Fuel Plans) when you need an actual stop-by-stop plan, and the Flow Diesel Prices tools for posted prices at specific truck stops (available on ValveRide partner API keys only). This tool is free and carries no charge.

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

Input Schema

NameRequiredDescriptionDefault
originNoOptional origin place string, e.g. "Dallas, TX" - used only to pick which states to include
destinationNoOptional destination place string

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description goes beyond them by disclosing data provenance (ValveRide Flow retail price grid), staleness (refreshed every 12 hours), and cost (free, no charge). It does not say what happens when origin/destination are omitted or unmatched, nor how 'typical optimized-savings context' is computed, leaving small behavioral gaps.

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 sentences, front-loaded with what the tool returns, then routing, then cost. Minor redundancy: 'This tool is free and carries no charge' restates the 'free' already implied and doubles the same point in one clause.

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 correctly spells out the return payload (median/p10/p90 plus per-state percentiles) and the zero-required-parameter behavior is implicitly safe. Slight incompleteness: it does not state what the response looks like when neither origin nor destination is supplied, which matters given both params are optional.

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% and the schema already explains that origin is used only to pick which states to include. The description echoes that ('per-state percentiles for any states mentioned in origin/destination') but adds no format, parsing, or matching semantics beyond the schema. 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?

States a specific resource (cached US diesel market snapshot) and the exact payload returned: national median/p10/p90 retail diesel and per-state percentiles. It also names the sibling tools it is not (optimize_fuel_plan, Flow Diesel Prices station tools), so an agent can discriminate without opening any schema.

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

Usage Guidelines5/5

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

Explicit routing guidance: use this for market questions or cost estimates, use optimize_fuel_plan for a stop-by-stop plan, and use the Flow Diesel Prices tools for posted prices at specific truck stops. It even flags that the third option requires ValveRide partner API keys, which prevents a doomed call.

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