Skip to main content
Glama
Sign In

FreightFA

by com.freightfa.mcp
OverviewDiscussionsAdmin

Estimate truckload (FTL) rate

estimate_truckload_rate
Read-only

Estimate a full-truckload freight rate for a lane using FreightFA's rate engine. Returns a directional benchmark for planning. Each call counts as one estimate toward the account's monthly FreightFA allowance.

Input Schema

NameRequiredDescriptionDefault
originNoOrigin city and state; provide with destination, or use both ZIPs.
weightYesShipment weight in pounds, or null.
distanceYesLane distance in miles. recommend_mode returns it for a city or ZIP pair.
origin_zipNo
request_idNorequest_id from recommend_mode for this lane, or null. Links the price to that search.
destinationNo
pickup_dateNoPickup date YYYY-MM-DD; omitted uses the calculator default.
equipment_typeYesEquipment type, e.g. 'Dry Van', 'Reefer', 'Flatbed', 'Dump Truck'.
destination_zipNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / destination
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 160,
+      "minLength": 2,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedInput schema / properties / destination_zip
      Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^[0-9]{5}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedInput schema / properties / origin
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 160,
+      "minLength": 2,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Origin city and state; provide with destination, or use both ZIPs."
+}
    • addedInput schema / properties / origin_zip
      Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^[0-9]{5}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedInput schema / properties / pickup_date
      Added value: +{
+  "anyOf": [
+    {
+      "format": "date",
+      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Pickup date YYYY-MM-DD; omitted uses the calculator default."
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / request_id
      Added value: +{
+  "anyOf": [
+    {
+      "format": "uuid",
+      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "request_id from recommend_mode for this lane, or null. Links the price to that search."
+}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover safety (readOnlyHint=true, destructiveHint=false) but not the metered cost, so 'each call counts as one estimate toward the account's monthly FreightFA allowance' is genuinely additive — it warns the agent to avoid redundant calls. 'Directional benchmark' also sets expectations on precision, though the actual response shape is left unstated.

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 purpose. The quota warning and the precision caveat are each a single clause with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter tool with no output schema, the description omits the location-input alternatives (origin/destination vs origin_zip/destination_zip) and says nothing about what the returned rate looks like beyond 'directional benchmark'. The quota note is a strength, but the input-mode ambiguity is a real 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?

At 67% schema coverage, the schema documents weight, distance, pickup_date, request_id, and origin, but leaves origin_zip, destination, and destination_zip bare. The description does not clarify the either/or input pattern (city pair vs ZIP pair) that the schema's param descriptions only hint at, so it adds nothing beyond the schema.

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 ('Estimate a full-truckload freight rate for a lane') and names the engine behind it (FreightFA). 'Full-truckload' immediately separates it from estimate_ltl_rate, estimate_rail_rate, estimate_barge_rate, and estimate_intermodal_rate among siblings.

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?

'Returns a directional benchmark for planning' implies the use case (rough planning, not a booked quote), which is useful context. But it never says when to prefer recommend_mode first, or when a different mode estimator is appropriate, and gives no exclusion cases.

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