Skip to main content
Glama

Estimate ELD switch savings

estimate_switch_savings
Read-onlyIdempotent

Estimate what a carrier saves per year by moving from their current ELD provider to ELD Hub at $15/truck/month, including a link to the provider's cancellation guide.

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": {
      "trucks": "<trucks>",
      "currentProvider": "<currentProvider>"
    },
    "name": "estimate_switch_savings"
  }
}

Input Schema

NameRequiredDescriptionDefault
trucksYesNumber of trucks in the fleet.
currentProviderYesCurrent ELD provider name, e.g. 'Motive'. Null uses a mid-tier average.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world, so safety is covered. The description adds genuinely useful context beyond that: the fixed $15/truck/month pricing assumption baked into the estimate and the fact that a cancellation-guide link is part of the result. It does not mention the 500-truck cap or that a null provider falls back to a mid-tier average, but both live in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler, front-loading the estimate and its unit ('per year') before the pricing assumption and the cancellation-guide link. Nothing repeats the schema or annotations.

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?

Two fully documented parameters, a read-only profile, and no output schema mean the description needs to hint at the return; it does so by naming the savings figure and the cancellation-guide link. It stops short of describing the shape of the estimate (breakdown vs. single number), which is the remaining gap.

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%, including the null-currentProvider fallback behavior, so the schema does the parameter work. The description adds only the pricing assumption and the per-year output period, which is marginal value over the structured fields. Baseline 3 applies.

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 specific verb ('Estimate') and a precisely scoped resource: annual carrier savings from switching to ELD Hub, with the assumed $15/truck/month rate named inline. That distinguishes it cleanly from siblings like compare_eld_providers, get_eld_pricing, and recommend_eld without needing to name them.

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 switching context implies when the tool applies (a carrier evaluating a move off their current provider), but there is no explicit when-to-use/when-not statement and no alternative tool is named. An agent must infer that this is the calculator rather than the pricing lookup or the comparison tool.

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