machship-mcp

Search Consignments

machship_search_consignments

Read-onlyIdempotent

Search consignments by Reference 1, Reference 2, or carrier ID to locate and retrieve matching shipment records.

Instructions

Searches consignments by reference numbers (Reference 1, Reference 2, or carrier IDs).

Args:

references (string[]): Array of reference strings to search for

Input Schema

Name	Required	Description	Default
`references`	Yes	Reference values to search

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.

Changed1 schema field changedv1.0.1Nov 3, 2026

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

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds nothing behavioral beyond that — no statement on whether references are matched exactly or partially, case sensitivity, mixed reference types in one call, or result limits.

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?

One front-loaded sentence that conveys the essentials, followed by an Args block that duplicates the schema. Short and readable, with only minor redundancy.

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?

An output schema exists, so return values need not be explained, and only one parameter is involved. Still missing is the crucial disambiguation from several near-identical sibling tools and any note on match semantics, which leaves the definition minimally viable rather than complete.

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 coverage is 100% and already describes 'Reference values to search'; the description's Args block merely restates the array of strings. It could have added which reference namespaces are searched (Reference 1, Reference 2, carrier ID) per element, but the semantics of matching remain unstated.

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 clear verb and resource ('Searches consignments') and names the three reference keys it accepts. However, it never distinguishes itself from the dedicated siblings machship_get_consignments_by_reference1, _by_reference2, and _by_carrier_id, which occupy nearly the same purpose space.

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?

There is no guidance on when to use this multi-key search versus the single-key get_consignments_by_reference1/2/carrier_id tools, nor versus get_consignments_by_ids or get_all_consignments. The agent must infer routing from names alone.

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

Deploy Server