Skip to main content
Glama
Sign In

FreightFA

by com.freightfa.mcp
OverviewDiscussionsAdmin

Get next week's national truck rate outlook

get_market_outlook
Read-onlyIdempotent

FreightFA's forecast for next week's U.S. national spot rate per mile (all-in including fuel) for dry van, reefer, or flatbed: the current weekly average, a p10/p50/p90 band, and whether rates look to be rising, falling, or stable, with the rationale and caveat. Omit the equipment type to get all three. National, not lane-specific. Does not count toward the estimate allowance.

Input Schema

NameRequiredDescriptionDefault
equipmentNoEquipment type. Omit or null for all three.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / equipment / anyOf
      Added value: +[
+  {
+    "enum": [
+      "dry_van",
+      "reefer",
+      "flatbed"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / equipment / description
      Previous value: -"Equipment type."New value: +"Equipment type. Omit or null for all three."
    • removedInput schema / properties / equipment / enum
      Removed value: -[
-  "dry_van",
-  "reefer",
-  "flatbed"
-]
    • removedInput schema / properties / equipment / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
-  "equipment"
-]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations establish the safe read-only/idempotent profile, and the description adds real context beyond them: the 'does not count toward the estimate allowance' quota behavior and the shape of the returned forecast including caveats. No contradiction with annotations.

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?

Front-loaded with the purpose before the payload details, and the scope and allowance caveats follow in a tight sequence. Dense but each clause carries information; no filler sentences.

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 carries the return-value burden by spelling out average, band, trend, rationale and caveat. A single optional parameter is fully covered, so an agent has enough to call it correctly; only the sibling-routing detail is thin.

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 enum-like parameter is fully documented in the schema, so the baseline is 3. The description's 'Omit the equipment type to get all three' merely restates the schema's 'Omit or null for all three' rather than adding new semantics.

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+resource ('forecast for next week's U.S. national spot rate per mile') and enumerates the exact payload (weekly average, p10/p50/p90 band, trend direction, rationale, caveat). 'National, not lane-specific' plus the named equipment types distinguish it from siblings like estimate_truckload_rate and get_rail_market_outlook.

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

Usage Guidelines4/5

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

Gives clear context: use for national aggregate view, not lane-specific work, and 'Omit the equipment type to get all three' tells the agent exactly how to widen the query. Also discloses that it does not consume the estimate allowance. It stops short of naming the sibling outlooks (rail, barge, index) as alternatives, so no explicit when-not routing.

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

All FreightFA 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