Skip to main content
Glama
Sign In

FreightFA

by com.freightfa.mcp
OverviewDiscussionsAdmin

Explain a freight market term

explain_freight_term
Read-onlyIdempotent

Plain-English definition of a freight market index, ratio, or charge from the FreightFA glossary: OTRI, OTVI, load-to-truck ratio, NTI, Cass Freight Index, RCAF, fuel surcharge, freight class, detention and demurrage, DIM weight, bill of lading, deadhead, accessorials, linehaul, and more. Returns who publishes it, how to read it, and why it matters. Omit the term to list every entry with its link. Does not count toward the allowance.

Input Schema

NameRequiredDescriptionDefault
termNoThe term or abbreviation, e.g. 'OTRI' or 'linehaul rate'. Omit or null to list every term.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / term / anyOf
      Added value: +[
+  {
+    "minLength": 2,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / term / description
      Previous value: -"The term or abbreviation, e.g. 'OTRI' or 'linehaul rate'."New value: +"The term or abbreviation, e.g. 'OTRI' or 'linehaul rate'. Omit or null to list every term."
    • removedInput schema / properties / term / minLength
      Removed value: -2
    • removedInput schema / properties / term / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
-  "term"
-]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world traits, so the bar is lower. The description adds value beyond them by disclosing return content (who publishes it, how to read it, why it matters) and a non-annotation behavioral attribute: that calls do not count toward the allowance.

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?

Purpose is front-loaded in the opening clause, and the long term enumeration, while lengthy, functions as a useful discovery aid for matching. The sentence structure is tight and each sentence carries information, though the example list is on the verbose side.

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 single-optional-param lookup tool with annotations and no output schema, the description is largely self-sufficient: it explains what is returned and the fallback behavior. Minor gaps remain around matching behavior (abbreviations vs. full names) and result format, but nothing essential 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% and the single `term` parameter is already documented with examples and the omit/null behavior in the schema. The description restates 'omit the term to list every entry' but adds no format or matching semantics (e.g. case sensitivity or fuzzy matching) beyond the schema. 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 deliverable (plain-English definition) and a specific resource (freight market index, ratio, or charge from the FreightFA glossary), with a concrete list of covered terms. An agent can distinguish this lookup tool from analysis tools like get_freight_index_outlook or ask_freight_analyst 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 Guidelines4/5

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

Gives clear context for use (defining/decoding a term) and explicitly describes the no-arg fallback behavior (omit the term to list every entry with its link). It does not, however, name sibling alternatives such as ask_freight_analyst for interpretive questions, so routing vs. those tools is left to inference.

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