Skip to main content
Glama

USDOT Operating Authority and Insurance Status Sentinel

Operating Authority Sentinel: authority lookup

authority_lookup
Read-onlyIdempotent

Use this when you need to check, before tendering a load or renewing a contract, whether a US motor carrier's operating authority is active and its insurance on file. For 1 to 10 USDOT numbers: authority per docket, BMC-91/34/84 filings, suspension notices and insurance cancellations with effective date and days left, next deadline. For carrier vetting. No personal data returned. Not a consumer report under the FCRA. Price: 0.01 USDC per call (x402). Free trial: set free_trial to true (3 calls per day per caller).

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": "authority_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
usdotYes1 to 10 USDOT numbers, comma-separated
free_trialNoSet to true to ask for the free trial (3 calls per day per caller, shared with the web route, within a daily cap for the service). Without it, the tool asks for an x402 payment.

Output Schema

NameRequiredDescriptionDefault
dataNoDatasets read live and the only fields used
noteNoHow to read found=false, notices, cancellations; which FMCSA record to check before acting
rulesNoRules applied, with official URL and status
licenceNoLicence of the source data: nom, url, source (attribution if required)
resultsNoOne entry per USDOT number: usdot_number, found, state, as_of, time_zone, time_zone_known, authorities (docket, authority_type, registry_status, last_event, same_day_conflict, registry_vs_history, insurance_requirements), policies_on_file (docket, form, coverage, insurer, effective_date, received_date, in_effect), suspension_notices (kind, served_on, effective_on, state, days_left, insurance_filing_received_since_served, first_seen_on), insurance_cancellations (form, reason: cancellation or replacement, cancellation_effective_on, state, days_left, newer_policy_on_file, newer_policy_effective_date, first_seen_on), next_deadline, official_record_url, authority_lookup_url
disclaimerNoNot legal advice; not affiliated with the FMCSA; not a consumer report

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / free_trial
      Added value: +{
      +  "description": "Set to true to ask for the free trial (3 calls per day per caller, shared with the web route, within a daily cap for the service). Without it, the tool asks for an x402 payment.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses key behavioral context: no personal data is returned, it is not a consumer report under the FCRA, and it returns authority per docket, filings, suspension notices, cancellations with effective dates and days left, plus next deadlines. It also explains pricing (0.01 USDC per call via x402) and the free-trial option with its 3-calls-per-day cap. This adds substantial operational and compliance context beyond readOnly/idempotent/openWorld hints.

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?

The use case is front-loaded and the description is dense but purposeful, covering purpose, outputs, privacy/FCRA caveat, pricing, and trial. A few phrases such as 'For carrier vetting' are slightly redundant, but there is little wasted text. The structure is readable and efficient.

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

Completeness5/5

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

Given an output schema and rich annotations, the description supplies everything an agent needs to decide when to call the tool, what it returns, and how payment/trial works. It also adds the important FCRA/privacy caveat that structured fields do not cover. No critical behavioral or contextual gap remains for this lookup tool.

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?

The input schema already documents both parameters at 100% coverage, including the USDOT pattern and the free_trial description. The description restates the 1-to-10 USDOT range and adds pricing/trial context, but does not add meaningful semantics beyond what the schema provides. A baseline 3 is appropriate when the schema carries the parameter documentation.

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?

The description states a specific verb and resource: checking whether a US motor carrier's operating authority is active and insurance is on file. It details the outputs (authority per docket, BMC-91/34/84 filings, suspension notices, insurance cancellations, next deadline) and scope of 1 to 10 USDOT numbers. It does not explicitly differentiate itself from sibling tools such as carrier_compliance_lookup, so it falls short of a 5.

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?

It gives clear triggering contexts: before tendering a load or renewing a contract, and for carrier vetting. It does not state when not to use it or name alternative tools for related carrier-compliance checks. The usage context is strong but lacks explicit alternatives or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.