machship-mcp

Get Consignment Tracking Statuses

machship_get_consignment_statuses

Read-onlyIdempotent

Retrieve tracking and delivery statuses for one or more consignments, with an optional ISO 8601 filter to limit results to statuses created since a given UTC datetime.

Instructions

Returns tracking/delivery statuses for a batch of consignments, with optional date filter.

Args:

ids (number[]): Consignment IDs
sinceDateCreatedUtc (string, optional): Only return statuses since this UTC datetime (ISO 8601)

Input Schema

Name	Required	Description	Default
`ids`	Yes	Consignment IDs
`sinceDateCreatedUtc`	No	Filter: only statuses since this UTC datetime (ISO 8601)

Output Schema

Name	Required	Description	Default
`errors`	No	Validation errors returned by Machship, if any
`object`	No	Response payload from the Machship API

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.1Nov 3, 2026

addedInput schema / properties / ids / items / maximum
```
Added value: +9007199254740991
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "errors": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Validation errors returned by Machship, if any"
+    },
+    "object": {
+      "description": "Response payload from the Machship API"
+    }
+  },
+  "type": "object"
+}

First observedv1.0.0Jun 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds nothing beyond that: no batch-size limits, no ordering of returned statuses, no statement about IDs that do not exist, and no note on whether only the latest status per consignment is returned.

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?

The opening sentence is front-loaded and small, with no filler. However, the Args list duplicates the input schema's own descriptions word-for-word, which is wasted space rather than added value.

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 low-complexity, two-parameter read tool with full schema coverage, an output schema and read-only annotations, the description is sufficient to invoke it correctly. The only real gap is operational detail about large ID batches, which is a minor omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the parameters are already documented, and the description's Args block restates the schema text verbatim. It adds no extra meaning such as maximum batch size, timezone expectations, or the effect of omitting sinceDateCreatedUtc.

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: returns tracking/delivery statuses for a batch of consignments, with the filter scope named. It is clearly distinct from machship_update_consignment_statuses (the write counterpart) by the word 'Returns', but it never explicitly names or contrasts that sibling.

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: 'batch of consignments' suggests it is the multi-ID status reader and the date filter suggests incremental polling. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. machship_get_consignment for a single consignment's full detail).

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

Deploy Server