Skip to main content
Glama
fleet-mcp-server

fleet-mcp-server

by Mahadhassan3

idling_report

Ranks vehicles by engine idle time over a selected period and estimates fuel cost, helping identify wasteful idling and target fuel savings.

Instructions

Rank vehicles by engine idle time over the last days days and estimate what that idling cost in fuel. Use this for questions about waste, fuel savings or idle outliers. fuel_price is dollars per litre.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo
fuel_priceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses that output is a ranking plus a cost estimate and that the window is the last `days` days, which is useful. It omits sort direction, whether the cost estimate is in dollars, permissions, and any rate/cost caveats.

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?

Three short sentences with no filler, and the primary action is front-loaded before the usage triggers. The trailing `fuel_price` unit note could be folded into the main sentence, but nothing is wasted.

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

Completeness3/5

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

With three optional parameters, no annotations, and no output schema, the description should say more about what the ranking returns and what `limit` does. The fuel-cost framing and lookback window are covered adequately, but the return shape and the top-N behavior are left to inference.

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 0%, so the description must compensate. It clarifies `days` as a lookback window and `fuel_price` as dollars per litre, which is genuinely additive. `limit` — the most consequential parameter for a ranking tool, defaulting to 5 — is left entirely unexplained.

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 gives a specific verb and resource: 'Rank vehicles by engine idle time' over the last `days` days, plus a secondary fuel-cost estimate. That is far more than a restatement of the name. It stops short of 5 because it never contrasts itself with siblings like vehicle_summary or driver_safety_scores, though those are clearly different domains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

'Use this for questions about waste, fuel savings or idle outliers' gives concrete when-to-use triggers keyed to the agent's intent. It offers no when-not conditions and names no alternative tool for adjacent questions (e.g. general vehicle stats), so it is clear context without exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.