CargoMind MCP Server

Overview Schema Source Related Servers Discussions Admin

list_vehicles

Filter own-fleet vehicles by status or city and return capacity, current load, driver hours remaining, and fuel to support dispatch and fleet planning.

Instructions

List own-fleet vehicles with capacity, current load, driver hours remaining and fuel.

Args:
    status: available, on_route or maintenance. Empty = all.
    city: Current city of the vehicle (name or alias). Empty = all.

Returns:
    {"status": "ok", "count", "vehicles": [{id, type, capacity_kg, remaining_capacity_kg, status,
    current_city, driver_name, driver_hours_today, driver_hours_remaining, fuel_pct, refrigerated}]}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No
`status`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It implies a safe read and enumerates returned fields, but says nothing about pagination, result limits, permissions, or ordering for a list tool, leaving real gaps against the no-annotation baseline.

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?

Front-loaded purpose sentence followed by clean Args/Returns blocks with no filler. The Returns block largely restates the existing output schema, which is mild redundancy, but it is not verbose.

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 only two optional parameters and an output schema already covering the return shape, the description supplies everything an agent needs to invoke the tool correctly. Only the missing behavioral details (limits, ordering) leave a small residual gap.

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 description coverage is 0%, so the schema contributes only titles and defaults. The description compensates by enumerating the status values (available, on_route, maintenance) and clarifying that city accepts a name or alias, which is meaningful added semantics.

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 own-fleet vehicles') plus the exact data surfaced (capacity, load, driver hours, fuel). 'Own-fleet' implicitly separates it from list_carriers, though no sibling is named explicitly, keeping it just short of 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?

Filter semantics are implied through the Args block ('Empty = all' for status and city), which tells the agent how to broaden results, but there is no statement of when to choose this over list_carriers, track_shipment, or other listing tools. Usage is inferable but not guided.

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

Deploy Server