Skip to main content
Glama
fleet-mcp-server

fleet-mcp-server

by Mahadhassan3

vehicle_summary

Summarize one vehicle's usage over a selected number of days: trips, distance, idle time, fuel, fuel economy, top speed, and active fault codes.

Instructions

Usage summary for one vehicle over the last days days: trips, distance, idle time, fuel, fuel economy, top speed and number of active fault codes.

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": {
      "vehicle_id": "<vehicle_id>"
    },
    "name": "vehicle_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
vehicle_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does real work by disclosing which aggregates are computed and that they span a caller-specified window, but it says nothing about failure behavior for an unknown vehicle_id, how 'idle time' or 'fuel economy' are defined, or whether missing telemetry yields zeros versus omissions.

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, front-loaded with the tool's purpose and followed by the metric list. Nothing is redundant and no wording needs trimming.

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?

For a simple two-parameter read tool with no output schema, the enumeration of returned metrics covers most of what an agent needs. However, the identifier format and the handling of the default `days` value are left to the bare schema, so it is adequate rather than complete.

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 schema only offers bare titles 'Days' and 'Vehicle Id'. The description usefully glosses `days` as the aggregation window, but leaves the identifier format (internal ID vs VIN) unspecified and does not repeat the schema's default of 7 days in prose.

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+resource ('Usage summary for one vehicle') and enumerates the exact metrics returned (trips, distance, idle time, fuel, fuel economy, top speed, fault codes), which distinguishes it from siblings like active_faults or idling_report. It stops short of explicitly naming which sibling to use instead, so the differentiation is inferential 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 phrase 'over the last `days` days' conveys that this is a windowed rollup for a single vehicle, but there is no when-to-use versus when-to-use-something-else guidance, no prerequisites (e.g. that the vehicle must exist or be visible to the caller), and no mention of the sibling reports it overlaps with.

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