Skip to main content
Glama
fleet-mcp-server

fleet-mcp-server

by Mahadhassan3

recent_trips

Retrieves recent trips for a vehicle, newest first, including driver, distance, idle minutes, fuel use, and top speed for fleet review.

Instructions

Most recent trips for one vehicle, newest first, with driver, distance, idle minutes, fuel and top speed.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
vehicle_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description must carry the safety and behavioral burden. It does useful work by disclosing the ordering guarantee ('newest first') and the shape of each trip record (driver, distance, idle minutes, fuel, top speed), but it says nothing about read-only nature, whether the limit is a hard cap or how many trips exist in total, or any auth/prerequisite requirements.

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?

A single front-loaded sentence with no filler; the scope, the ordering behavior, and the returned fields all appear immediately. It is slightly dense as a fragment, but nothing in it is redundant.

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?

The output schema means return values need not be explained, yet the description lists them anyway, while the more consequential gaps remain: no annotations means the mutation/safety profile and the limit parameter semantics go unaddressed. For a two-parameter read tool this is adequate but incomplete.

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%, so both parameters are undocumented in structured fields. The description only implicitly covers vehicle_id ('for one vehicle') and adds nothing about its expected format (internal ID vs. external identifier), and it never mentions the limit parameter or its default of 10, leaving a quarter of the tool's contract 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 resource and scope: recent trips for exactly one vehicle, returned newest first, with a named set of fields. That is enough to distinguish it from list-style siblings such as list_vehicles or aggregate reports like idling_report, though it never explicitly contrasts itself with vehicle_summary.

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 by the phrase 'for one vehicle' and by the concept of recency; there is no statement of when to prefer this over idling_report or vehicle_summary, and no mention of when recency or a limit is inappropriate. An agent can guess the context but gets no explicit routing guidance or exclusions.

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