Skip to main content
Glama
fleet-mcp-server

fleet-mcp-server

by Mahadhassan3

active_faults

List active engine fault codes across a fleet, most severe first, with optional severity filtering to support maintenance triage.

Instructions

Active engine fault codes across the fleet, most severe first. Optionally filter by severity: low, medium or high. Use this for maintenance triage.

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

Input Schema

NameRequiredDescriptionDefault
severityNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: results are fleet-wide, restricted to currently active faults, and pre-sorted by severity. It does not state that this is a read-only query, whether results are paginated or capped, or how fresh the data is, leaving the safety and volume profile unstated.

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?

Three short sentences, front-loaded with the resource and scope, then the filter, then the use case. Nothing is padded and every clause carries information.

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?

For a one-parameter read tool with an output schema, this covers resource, scope, ordering, filter values, and purpose. The remaining gaps are minor: it does not say whether counts or vehicle identifiers accompany each fault, nor whether the list is truncated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the severity parameter is a bare string with no enum. The description partially compensates by naming the accepted values (low, medium or high) and marking the filter optional, which is the single most useful thing it could add. However, it omits case sensitivity, invalid-value behavior, and what the default (null) returns.

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?

"Active engine fault codes across the fleet" gives a specific resource and verb-phrase, plus an ordering guarantee ("most severe first") that no sibling offers. It is clearly distinct from the listed siblings, though it never names a boundary against a similar diagnostic tool, so a 4 rather than a 5.

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?

"Use this for maintenance triage" supplies a genuine use-case cue, which is more than nothing. But there is no when-not guidance, no mention of whether another tool covers historical faults or per-vehicle drill-down, so the agent must infer scope boundaries.

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