Skip to main content
Glama
Sign In
TruckerFetch MCP

TruckerFetch MCP

Official
by truckerfetch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

list_authorities

Read-only

Lists published operating authorities for a single U.S. motor carrier by USDOT number, with pagination to review results.

Instructions

List published operating authorities for one carrier.

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": {
      "usdot": "<usdot>"
    },
    "name": "list_authorities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
usdotYes
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that the description only adds the 'published' scope; it says nothing about result volume, pagination via the cursor, or whether an empty list vs. error is returned for an unknown carrier.

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?

A single front-loaded sentence with no filler, which is structurally clean. The brevity is efficient though it comes at the cost of the missing pagination and parameter context noted elsewhere.

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

Completeness2/5

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

For a three-parameter list tool with no parameter descriptions and no output schema, the definition does too little: pagination semantics and the identity/format of the required key are absent. A one-line description cannot carry this tool alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters. The description hints that the carrier is identified somehow but never names the USDOT number, its numeric pattern, the 1-100 limit, or that cursor is a pagination token.

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 verb and resource ('List published operating authorities') and scopes it to 'one carrier', which is enough to tell it apart from siblings like list_editions or search_carriers. The 'published' qualifier also signals a filtered subset rather than all authorities.

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

Usage Guidelines2/5

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

No guidance on when to choose this over get_carrier, list_authority_watch_targets, or search_carriers, and no prerequisites stated. The agent must infer that a USDOT number is required input from 'for one carrier' alone.

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

Deploy Server

Other Tools