Skip to main content
Glama
fleet-mcp-server

fleet-mcp-server

by Mahadhassan3

driver_safety_scores

Ranks drivers by safety scores from harsh-driving and speeding events per 100 km over a set period, returning lowest scores first to prioritize coaching.

Instructions

Driver safety scores (0-100, higher is safer) from harsh-driving and speeding events per 100 km over the last days days. Returned lowest score first, so the drivers who most need coaching come first.

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

Input Schema

NameRequiredDescriptionDefault
daysNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose useful behavior beyond structure: the 0-100 scale, higher-is-safer direction, the event basis and normalization per 100 km, and that results are sorted ascending by score. It does not state that this is a read-only report, how drivers with zero distance or zero events are handled, or whether pagination/limits apply.

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?

Two sentences with no filler: the first front-loads what the number means and how it is computed, the second explains ordering and why that ordering matters. Every clause adds information an agent would otherwise have to guess.

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 an output schema present, return-value details need not be described, and the description covers metric definition, window, and sort order well. Minor residual gaps remain around which drivers are included (all vehicles vs. only those with recorded driving) and whether results are truncated.

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?

Only one parameter exists and the schema has 0% description coverage, so the description must explain `days`. It does so implicitly by saying scores are computed 'over the last `days` days,' clarifying that the window is trailing/rolling rather than calendar-based. It does not state the default (30) or any bounds, but the core semantic of the parameter is covered.

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?

The description names a specific resource (driver safety scores) and defines the metric precisely: a 0-100 scale where higher is safer, derived from harsh-driving and speeding events per 100 km over a window. That combination of scale, direction, and derivation is unusually specific and makes it clearly distinct from report siblings like idling_report or active_faults.

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 guidance against alternatives, but the closing clause ('the drivers who most need coaching come first') implies a coaching/triage use case. An agent can infer the intent but is not told what other tool to reach for if it wants aggregate fleet safety rather than a per-driver ranking.

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