Skip to main content
Glama
fleet-mcp-server

fleet-mcp-server

by Mahadhassan3

list_vehicles

List fleet vehicles, optionally filtered by depot such as Ottawa, Toronto, or Montreal. Use it to retrieve available vehicles before answering depot-specific fleet questions.

Instructions

List vehicles in the fleet, optionally filtered by depot (Ottawa, Toronto, Montreal).

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

Input Schema

NameRequiredDescriptionDefault
depotNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

With no annotations, the description must carry the behavioral burden; 'List' implies a read-only, non-mutating operation, which is helpful but only inferred. It omits pagination, result limits, and whether an unfiltered call returns the entire fleet — meaningful gaps for a list endpoint, though an output schema exists so return formatting need not be described.

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 that front-loads the core action and appends the filter detail with zero filler. Nothing could be trimmed without losing 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-optional-parameter list tool with an output schema, the definition covers purpose, filter domain, and optionality adequately. The remaining gap is behavior on unfiltered or paginated calls, which matters more here because no annotations supply that context.

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?

Schema coverage is 0% and the single 'depot' parameter is an unconstrained string in the schema, so the description's enumeration of accepted values (Ottawa, Toronto, Montreal) adds genuine meaning the schema lacks. It does not specify case sensitivity or what happens for an unrecognized depot, keeping it below a 5.

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 and resource ('List vehicles in the fleet') plus the scope of filtering, which is unambiguous. It stops short of distinguishing itself from siblings like vehicle_summary, so an agent can't fully rule out overlap without reading schemas.

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

Usage Guidelines2/5

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

The word 'optionally' implicitly signals the filter can be omitted, but there is no explicit when-to-use guidance and no mention of alternatives such as vehicle_summary. Nothing tells the agent which tool to pick for fleet enumeration versus per-vehicle detail.

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