Skip to main content
Glama

Check whether an ELD is required

check_eld_requirement
Read-onlyIdempotent

Determine whether a vehicle needs an FMCSA electronic logging device: takes vehicle type, gross weight, operating radius, interstate status and CDL status, and returns whether the ELD mandate applies, which exemption fits, and why a broker may still require a connected ELD anyway.

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": {
      "vehicle": "<vehicle>",
      "grossWeightLbs": "<grossWeightLbs>",
      "interstate": "<interstate>",
      "airMileRadius": "<airMileRadius>"
    },
    "name": "check_eld_requirement"
  }
}

Input Schema

NameRequiredDescriptionDefault
vehicleYesVehicle type, e.g. 'sprinter van', 'cargo van', 'box truck', 'pickup truck / hotshot', 'semi truck'.
interstateYesTrue if the vehicle crosses state lines or hauls interstate commerce. Null if unknown.
airMileRadiusYesTypical operating radius from the home terminal in air miles. Null if unknown.
grossWeightLbsYesGross vehicle weight rating, or combined rating when towing, in pounds. Null if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description's job is to add context beyond that. It does: it discloses the three-part return (mandate applicability, which exemption fits, and the broker-requires-connected-ELD caveat), which is valuable since no output schema exists. It does not mention how null/unknown inputs affect the answer, which is the one behavioral gap.

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 front-loaded sentence that leads with the decision being made and then the inputs and outputs. The enumeration of all five inputs is partly redundant given 100% schema coverage and would be the first thing to cut, but nothing is padded.

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 no output schema, the description correctly spends its space describing the return values, which is what an agent needs. Missing only guidance on the CDL-status discrepancy and on how partially-unknown inputs (nulls) are resolved.

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 baseline is 3 and the schema already explains each field including null-as-unknown semantics. The description adds little beyond restating the fields, and it lists a 'CDL status' input that does not exist in the schema (additionalProperties: false), which could mislead an agent into passing an invalid parameter.

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

Purpose5/5

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

States a precise verb + resource ('Determine whether a vehicle needs an FMCSA electronic logging device') and names the exact regulatory question answered. This is clearly distinct in scope from siblings like recommend_eld (provider selection) and get_hos_rules (hours-of-service rules), so an agent can route without opening a schema.

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: the description suggests this is the applicability pre-check that precedes choosing a provider, but it never says so. No alternative is named (e.g. 'run this before recommend_eld') and no exclusions or prerequisites are given.

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