Skip to main content
Glama

Check broker / vetting platform ELD integration

check_broker_integration
Read-onlyIdempotent

Answer whether an ELD HUB account satisfies a broker or carrier-vetting platform that requires a connected ELD — Highway, Trucker Tools, and broker-side vetting generally — and return the exact setup steps, pricing and hardware availability.

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": {
      "platform": "<platform>"
    },
    "name": "check_broker_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesPlatform or broker name, e.g. 'Highway', 'Trucker Tools', 'RMIS', or a broker's name. Null for a general answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the response is not just a boolean but includes exact setup steps, pricing and hardware availability — important given there is no output schema. It does not discuss coverage limits or freshness of the integration data.

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 sentence with the core question front-loaded before the return-value clause; no filler. It is long but every clause carries information about scope or output. Slight density cost from cramming platform examples and return contents into one sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, read-only lookup with no output schema, the description covers what the tool answers, which platforms it covers, and what the response contains. An agent has enough to select and call it correctly; remaining gaps (data freshness) are minor.

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?

With one parameter at 100% schema description coverage, the schema already explains the 'platform' argument and gives examples. The description reinforces the accepted input space ('Highway, Trucker Tools, and broker-side vetting generally') and hints that null yields a general answer, but adds no format or matching semantics beyond that. 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?

The description states a specific verb-and-resource pair: answer whether an ELD HUB account satisfies a broker/vetting platform's connected-ELD requirement, and return setup steps, pricing and hardware availability. Scope is concrete and named examples (Highway, Trucker Tools) make the domain obvious. It stops short of naming the closest siblings (check_eld_requirement, check_hardware_compatibility), so differentiation is inferred 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the tool is for broker/vetting-platform questions, and the schema notes 'Null for a general answer.' There is no explicit when-to-use vs when-to-use-a-sibling guidance, such as routing generic ELD-requirement questions to check_eld_requirement or device questions to check_hardware_compatibility. An agent must infer the boundary from the tool name and examples.

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