Skip to main content
Glama

USDOT MCS-150 Biennial Update Deadline Sentinel

MCS-150 biennial update deadline: free sample

mcs150_example
Read-onlyIdempotent

Free sample: a real answer for one carrier, same shape as mcs150_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": "mcs150_example"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds two genuinely new facts beyond that: it is free (no quota/cost) and it returns 'one carrier' only. It says nothing about which carrier is sampled or whether the result is fixed versus live.

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 short sentence with no filler, and the most decision-relevant word ('Free sample') is front-loaded. It is efficient but borders on under-specification rather than tightness.

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 zero parameters, rich annotations and an output schema, the description only needs to explain what the sample is and when it applies. It fails to say whether the sample carrier is fixed and how its output differs from a live lookup, which is the one ambiguity an agent calling this tool would have.

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 per-parameter meaning for the description to add; baseline 4 applies. The mention of 'one carrier' is scope framing, not a parameter, and does not misrepresent the 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?

The description never names the verb or the resource explicitly -- the MCS-150 biennial deadline appears only in the title. It does convey scope ('a real answer for one carrier') and differentiates from the sibling by saying the result has 'same shape as mcs150_lookup', so an agent can roughly place it, but the core action is implied rather than stated.

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?

'Free sample' hints at demo/trial usage but gives no explicit when-to-use, when-not-to-use, or guidance on choosing this over mcs150_lookup for a real carrier query. The agent must infer that this is for previewing output shape rather than doing substantive lookups.

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.