CargoMind MCP Server

Overview Schema Source Related Servers Discussions Admin

list_shipments

Query shipments with filters for status, city, priority, and limit. Results sorted active first, critical first, then earliest promised delivery.

Instructions

List shipments, filtered and sorted (active first, critical first, then earliest promised delivery).

Args:
    status: One of created, picked_up, in_transit, delayed, out_for_delivery, delivered, exception,
        or "active" (anything not yet delivered/exception). Empty = all.
    city: City name or alias (e.g. "Bangalore", "Bombay"); matches origin, destination or current city.
    priority: standard, express or critical. Empty = all.
    limit: Maximum rows to return (default 25).

Returns:
    {"status": "ok", "count": n, "shipments": [...]} each with is_late / delay_hours.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No
`limit`	No
`status`	No
`priority`	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.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the sort order and the response shape with is_late/delay_hours, which is useful. However, it doesn't state read-only nature explicitly, permission requirements, or pagination behavior (only a limit default).

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 with the core action and sort order, then organized Args/Returns. Slightly verbose with the multi-line enum listing but every element is informative.

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?

Even without an output schema-explain requirement (it has one, though the description still describes the wrapper), the description covers filtering, sorting, and return shape adequately. Missing only explicit safety/read-only statement and cross-sibling guidance.

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%, so the description must compensate – and it does well: it enumerates status values including the 'active' pseudo-value, explains city alias matching across origin/destination/current city, and gives the limit default. Only priority lacks an explicit default note (empty = all is stated).

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?

States a specific verb+resource ('List shipments') and adds the implicit sort order (active first, critical first, then earliest promised delivery), which distinguishes it from track_shipment and update_shipment_status.

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 implied by the filtering args (status/city/priority/limit), but there is no explicit 'when to use vs track_shipment/shipment_history' guidance or exclusions. The agent can infer this is a filtered list, but the sibling routing is left to inference.

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

Deploy Server