Lane Cost freight rates

Rate history for a truck type

get_rate_history

Read-onlyIdempotent

Rate per mile for one truck type and its monthly history: national, or for freight leaving or entering one state. Per-mile rates are for a 750-mile haul.

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": {
      "equipment": "<equipment>"
    },
    "name": "get_rate_history"
  }
}

Input Schema

Name	Required	Description
`state`	No	Two-letter code of a lower-48 state, such as TX. Leave out for the national rate.
`months`	No	How many of the most recent months to return. Default 24. History starts 2003-12.
`direction`	No	With state: freight leaving it (default) or entering it.
`equipment`	Yes	Truck type. Required.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare a read-only, idempotent, closed-world read, so the safety profile is covered. The description adds genuinely useful context beyond that: rates are per-mile, and normalized to a 750-mile haul, which tells the agent how to interpret the numbers. It stops short of describing output shape or history granularity beyond 'monthly'.

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 short sentences, front-loaded with the primary result (per-mile rate) and followed by the interpretation caveat. No filler, no repetition of the title, and every clause carries scoping or semantic 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, the description must speak for the return value, and 'monthly history' plus 'per-mile rates ... 750-mile haul' gives enough to interpret the series. Minor gaps remain: currency/unit expectation and whether history is returned as a continuous series are left implicit, but nothing needed to invoke the tool correctly is missing.

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 description coverage is 100%, with enums for equipment and direction and explicit defaults/limits for months, so the schema carries the parameter burden. The description corroborates the national-vs-state and inbound/outbound semantics but adds no format or edge-case detail beyond what the schema states. Baseline 3 applies.

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?

States a specific resource and dimension: per-mile rate plus monthly history for a single truck type, national or single-state. The 750-mile reference adds scope precision. It does not, however, name or contrast itself with siblings like get_state_rates, get_national_rates, or get_lane_rate_history, which cover overlapping ground.

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 implied by the scope wording ('national, or for freight leaving or entering one state'), so an agent can infer the state/direction switch. But there is no explicit when-to-use guidance against the sibling rate tools, no statement of what this tool cannot do (e.g., lane-level or multi-state queries), and no prerequisites noted.

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 tools Inspect

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

Need Help?