Skip to main content
Glama

USDOT MCS-150 Biennial Update Deadline Sentinel

MCS-150 biennial update deadline lookup (USDOT)

mcs150_lookup
Read-onlyIdempotent

Use this when you need to know whether a US motor carrier's biennial MCS-150 update is due or overdue. For 1 to 10 USDOT numbers: next and last filing deadline (49 CFR 390.19T), days left in the carrier's state time zone, overdue flag, USDOT status, and deactivation enforcement: the FMCSA suspended it for updates due since 2026-06-01 and is unclear on earlier ones (notice, quote and read date returned). No personal data returned. Not a consumer report under the FCRA. Price: 0.005 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": "mcs150_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
dataNoData source and the only fields read
noteNoPRISM exemption and how to read null values
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, usdot_status (active, inactive, pending), state, operation (interstate, intrastate_hazmat, intrastate_non_hazmat), covered_by_390_19T, as_of, time_zone, time_zone_known, filing_month, filing_years (odd, even), parity_assumed, last_deadline, next_deadline, days_to_next_deadline, last_mcs150_update, overdue (true, false, null), overdue_reason, deactivation_exposure (true, false, null), deactivation_exposure_reason, enforcement_for_last_deadline (suspended: due on or after enforcement.since, covered by the FMCSA notice; not_explicitly_covered: due earlier, the notice neither covers nor excludes it explicitly; not_suspended: computed before the notice existed), safer_url
disclaimerNoNot legal advice; not affiliated with the FMCSA; not a consumer report
enforcementNoWhat the FMCSA says it currently enforces: state (suspended), since (first due date explicitly covered), until, applies_to, rule_still_in_force, source_url, source_last_updated, read_on, quote, summary_url, summary_read_on, summary_quote (the FMCSA Resources Hub summary of the notice)

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 readOnly/idempotent/openWorld annotations, the description discloses cost (0.005 USDC per call via x402), a rate-limited free tier (3 calls/day/caller, shared with the web route), privacy posture (no personal data), a regulatory disclaimer (not an FCRA consumer report), and a temporal enforcement caveat about FMCSA suspension for updates due since 2026-06-01. That is substantial context an agent cannot derive from the annotations or schema.

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 first sentence front-loads the use case, and the remaining sentences each carry distinct value (returned fields, privacy, FCRA, price, free trial). The returned-fields sentence is a dense run-on that takes effort to parse, which slightly hurts readability, but there is no filler.

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?

With annotations, a full schema, and an output schema in place, the description covers the remaining agent-relevant concerns: cost, trial limits, data handling, and enforcement timing. Only minor gaps remain, such as what 'USDOT status' values mean and error behavior for invalid or unknown numbers.

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 coverage is 100%, so the schema already documents both parameters, including the 1-10 comma-separated USDOT range and the free_trial behavior. The description restates the 1-10 range and the 3-calls-per-day trial limit without adding new syntax or format detail. Baseline 3 applies when the schema does the heavy lifting.

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 precise verb and resource: a lookup of whether a US motor carrier's biennial MCS-150 update is due or overdue, scoped to 1-10 USDOT numbers. It also enumerates the returned fields (next/last deadline, days left, overdue flag, USDOT status), which makes the tool unmistakable. It never mentions the mcs150_example sibling, so explicit sibling differentiation is absent.

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?

"Use this when you need to know whether a US motor carrier's biennial MCS-150 update is due or overdue" gives a clear triggering condition. The free-trial sentence also routes the caller on how to invoke it cheaply. There are no explicit when-not-to-use conditions or named alternatives.

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.