Skip to main content
Glama

USDOT Operating Authority and Insurance Status Sentinel

Operating Authority Sentinel: free sample

carrier_compliance_example
Read-onlyIdempotent

Free sample: a real answer for one large motor carrier, same shape as carrier_compliance_lookup.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "carrier_compliance_example"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataNoThe six datasets read live and the only fields used
noteNoHow to read both blocks; which FMCSA records to check before acting
rulesNoRules applied by both blocks, with official URL, status and block
licenceNoLicence of the source data: nom, url, source (attribution if required)
resultsNoOne entry per USDOT number: usdot_number; authority (exactly the /v1/authority entry for the number); biennial_update (usdot_status, operation, covered_by_390_19T, as_of, time_zone, filing_month, filing_years, last_deadline, next_deadline, days_to_next_deadline, last_mcs150_update, overdue, overdue_reason, deactivation_exposure, enforcement_for_last_deadline); as_of_differs_between_blocks; deadlines (kind: suspension_notice, insurance_cancellation or biennial_update; date; days_left; as_of; time_zone; enforcement for the biennial update), sorted by date
disclaimerNoNot legal advice; not affiliated with the FMCSA; not a consumer report
enforcementNoWhat the FMCSA says it enforces for the biennial update, quoted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile needs no restating. The description adds genuinely new context: the result is for a single fixed large motor carrier and is a sample, meaning output is not tailored to the caller. It stops short of saying whether the sample data is static or refreshable, or that it must not be presented as a real compliance determination.

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 clipped sentence with no filler; the sample caveat is front-loaded ahead of the output-shape comparison. The telegraphic style (fragment, no verb) costs a little clarity, but nothing is redundant.

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?

With an output schema present and zero parameters, the description does not need to document return values or arguments, and annotations cover the safety profile. The remaining gap is material for this tool type: nothing warns that the sample must not be reused as a real compliance answer for a different carrier, which is the main misuse risk here.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description does implicitly reinforce this by describing an answer for "one" carrier rather than a filterable query, which matches the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Free sample: a real answer for one large motor carrier" tells the agent this returns a fixed illustrative compliance result rather than a queried one, and "same shape as carrier_compliance_lookup" ties it to the sibling's output format. However, it never names the subject matter of the answer (operating authority status, compliance fields), so the agent must infer the resource from the title rather than the description.

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?

Calling it a "free sample" with the same shape as carrier_compliance_lookup implicitly signals it should be used to preview output rather than to look up a specific carrier, which is useful routing information. There is no explicit statement of when to prefer this over the lookup sibling or that it cannot answer a query about an arbitrary carrier, so the guidance remains inferred rather than stated.

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.