Skip to main content
Glama

Get FMCSA hours-of-service rules

get_hos_rules
Read-onlyIdempotent

Return the current FMCSA hours-of-service limits for property-carrying or passenger-carrying CMV drivers: the 11-hour driving limit, 14-hour on-duty window, 30-minute break, 60/70-hour weekly cap, 34-hour restart, sleeper-berth split and the 150 air-mile short-haul exception.

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": {
      "driverType": "<driverType>"
    },
    "name": "get_hos_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
driverTypeYesType of CMV driver. Null defaults to property-carrying (freight).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, closed-world lookup, so the safety profile is covered. The description adds that it returns 'current' limits and names which limits are in the payload, which is useful, but says nothing about jurisdiction scope, citation dates, or whether it covers state variations.

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?

One dense, front-loaded sentence with the verb and resource first and the returned rule set as an appositive list. The list is long but each item is substantive content, not filler, so nothing meaningful could be trimmed.

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 a single required parameter, no output schema, and annotations covering read-only/idempotent behavior, the description carries the return-content burden — and it does so by enumerating the limits returned. Only gaps are jurisdiction/scope and update cadence, which are minor for a static reference 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?

Schema description coverage is 100% and already documents driverType with its property/passenger enum and the null-defaults-to-property behavior. The description's phrase 'property-carrying or passenger-carrying CMV drivers' echoes the same distinction without adding format or edge-case detail beyond the schema, so baseline 3 applies.

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?

States a specific verb ('Return') and resource ('the current FMCSA hours-of-service limits') and enumerates the exact rule set, so the operation is unambiguous. No explicit sibling differentiation is needed here since the only near-neighbor (check_eld_requirement) is clearly a different question, but the description doesn't call that out itself.

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?

Usage is only implied — an agent can infer this is a reference lookup to be used when a compliance question arises, but there is no statement of when to prefer it over check_eld_requirement or other compliance siblings, and no exclusions or prerequisites.

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.

Resources