Skip to main content
Glama

USDOT Operating Authority and Insurance Status Sentinel

Operating Authority Sentinel: free sample

authority_example
Read-onlyIdempotent

Free sample: a real answer for one large motor carrier, same shape as authority_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": "authority_example"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds useful context that the answer covers one large motor carrier and matches authority_lookup's shape, but it still does not say whether the sample data is canned, which carrier it covers, or any usage limits.

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?

A single sentence, front-loaded with "Free sample" and without wasted wording. It states the sample nature and shape parity in one compact statement.

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?

This is a simple zero-parameter sample tool with an output schema and annotations that cover safety and mutability. The description sufficiently establishes its demo nature and parity with authority_lookup; only the fixed carrier identity and sample-data limitations are missing.

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 no parameter meaning for the description to add beyond the empty schema. The baseline for a zero-parameter schema is 4.

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?

The description identifies this as a free sample that mirrors authority_lookup, but it never says explicitly what resource is being looked up or what a "real answer" contains. "Operating Authority" appears only in the title, not in the description, so the purpose remains somewhat vague.

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?

It implies the tool is a demo sample by saying "free sample" and "same shape as authority_lookup," but it gives no explicit guidance on when to use this instead of authority_lookup or when not to use it. The agent must infer the preview use case.

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.