Skip to main content
Glama

Get ELD Hub pricing

get_eld_pricing
Read-onlyIdempotent

Return ELD Hub's verified pricing: $15/truck/month software with no contract, PT-30 and IOSiX hardware at $150 each with free shipping, package contents, three-year total cost and sign-up URL.

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": "get_eld_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 cover readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is handled. The description adds real value by declaring the response contents (per-truck software price, per-unit hardware price, shipping terms, package contents, three-year TCO and sign-up URL) that would otherwise be invisible since there is no output schema.

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 with no preamble or filler; the resource is named before the payload list. The tail is a dense comma-separated enumeration ('package contents, three-year total cost and sign-up URL') that borders on a run-on but each item earns its place by naming a return field.

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 and no parameters, the description carries the burden of telling the agent what comes back, and it does so concretely. Minor gaps remain: it does not say whether the figures are static or time-stamped, or note that this is a read that needs no setup, but nothing required to invoke it correctly is missing.

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 nothing for the description to disambiguate and the baseline of 4 applies. The schema is trivially complete for an empty object.

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 a specific resource (ELD Hub's verified pricing), and the explicit vendor attribution ('ELD Hub's') distinguishes it from comparison siblings like compare_eld_providers and recommend_eld. It stops short of naming those siblings, so the differentiation is implicit 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?

There is no explicit when-to-use or when-not-to-use statement; usage is only inferred from the enumerated content (pricing, hardware cost, TCO, sign-up URL). An agent can guess this is the pricing-lookup tool rather than the comparison or signup tool, but the description never routes it away from compare_eld_providers or start_signup.

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