Skip to main content
Glama

Lane Cost freight rates

A lane's price history

get_lane_rate_history
Read-onlyIdempotent

Month-by-month estimated price for one lane and one truck type, to show whether today's price is high or low. Figures are modeled estimates of the all-in price (linehaul plus fuel) for one full truckload of standard freight, in US dollars. They are not quotes.

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": {
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "get_lane_rate_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNoHow many of the most recent months to return. Default 24. History starts 2003-12.
originYesThe pickup place: a city and state such as "Chicago, IL", or a 5-digit ZIP. Lower 48 states only. A city alone picks the largest of that name; the result says which place was used.
equipmentNoTruck type. Default dry-van.
destinationYesThe delivery place: a city and state such as "Chicago, IL", or a 5-digit ZIP. Lower 48 states only. A city alone picks the largest of that name; the result says which place was used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), and the description adds genuinely useful non-obvious context: figures are modeled all-in estimates in USD, not quotes, and coverage is limited to the lower 48. It does not discuss normalization, missing months, or how the series is smoothed, but the added caveat is real value beyond the annotations.

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?

Three short sentences, front-loaded with what is returned and why, followed by the estimation caveat. No redundancy with the title and no filler.

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 four-parameter read-only lookup with full schema documentation and no output schema, the definition is nearly complete: scope, units, estimation status, and geography are covered. A short note on series granularity or absent months would close the last 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%, with defaults, history start date, enum, and geocoding behavior all documented in the parameters themselves. The description adds only the 'one full truckload of standard freight' basis and unit clarification, which is marginal beyond the schema baseline.

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 — month-by-month estimated price history for one lane and one truck type — plus the purpose (judging whether today's price is high or low). The 'estimated, not quotes' framing and lane/equipment scoping distinguish it from siblings like estimate_lane_rate (a point estimate) and get_rate_history.

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 stated use case ('to show whether today's price is high or low') implies when to reach for a time series rather than a single estimate, but it never explicitly contrasts with estimate_lane_rate or get_rate_history, nor does it state exclusions such as non-contiguous US lanes.

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