Skip to main content
Glama
Sign In

Lane Cost freight rates

by com.lanecost
OverviewDiscussionsAdmin

Diesel price

get_diesel_price
Read-onlyIdempotent

The US average on-highway diesel price per gallon (EIA): the latest week and recent months. It is the fuel input to every estimate.

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

Input Schema

NameRequiredDescriptionDefault
monthsNoHow many of the most recent months to return. Default 24. History starts 2003-12.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuine context beyond them: the authoritative source (EIA), the geographic scope (US average on-highway), and the weekly cadence of the series.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with no filler; the data definition and scope come first, and the trailing sentence earns its place by signalling downstream use in estimates.

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?

For a simple single-parameter read with rich annotations, the description supplies source, geography, units and cadence. It could note the currency or that the series is a weekly average observation set, but with no output schema required this is a minor gap.

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 single 'months' parameter is fully documented in-schema with its default of 24 and history start of 2003-12. The description only echoes 'recent months', adding no format or boundary detail beyond the schema, so the 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 with its exact definition: 'US average on-highway diesel price per gallon (EIA)', plus the time scope ('latest week and recent months'). An agent can tell this apart from the sibling rate tools (lane/national/state rates) without opening the schema.

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?

'It is the fuel input to every estimate' implies the context in which to reach for it, but there is no explicit when-to-use versus when-not guidance and no named alternative. Usage is inferable rather than stated.

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

All Lane Cost freight rates toolsInspect
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.

Resources