Skip to main content
Glama

Check ELD hardware compatibility

check_hardware_compatibility
Read-onlyIdempotent

Check whether an existing ELD device (PT-30, IOSiX ELD-BT/ELD-DX, or another provider's gateway) can be re-registered to ELD Hub, or buy a new PT-30 or IOSiX for $150 each with free shipping (IOSiX device only, PT-30 with cable).

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": {
      "device": "<device>"
    },
    "name": "check_hardware_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceYesDevice or provider name, e.g. 'PT-30', 'IOSiX ELD-BT', 'Samsara VG34'.

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 declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that the check covers re-registration eligibility and mentions purchase options, but it does not clarify the return format or whether the tool itself initiates any purchase action.

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 description is a single front-loaded sentence with the core purpose stated first. It is efficient, though the embedded pricing and shipping details are somewhat tangential to a compatibility-check tool.

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?

For a simple read-only tool with one fully documented parameter, the description is largely complete: it states what is checked and gives examples. It could be improved by clarifying the return value, but annotations and schema already cover most structured context.

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%, so the single 'device' parameter is already well documented with examples. The description repeats similar examples and adds no syntax or format details beyond what the schema provides, so the baseline of 3 is appropriate.

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 specific verb and resource: checking whether an existing ELD device can be re-registered to ELD Hub. It names example devices and purchase options, making the tool's scope clear, though it does not explicitly distinguish itself from siblings like compare_eld_providers or get_eld_pricing.

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?

The description implies usage by describing two scenarios: re-registering an existing device or buying a new one. However, it gives no explicit guidance on when to choose this tool over siblings such as compare_eld_providers, get_eld_pricing, or recommend_eld.

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