machship-mcp

Create Consignment with Complex Items

machship_create_consignment_with_complex_items

Create consignments using detailed item packaging and dangerous goods data for accurate freight booking. Use for shipments requiring complex item definitions beyond standard items.

Instructions

Creates a consignment using complex item definitions (with detailed packaging/dangerous goods data).

Args:

consignment (object): Consignment data with complexItems array instead of standard items

Input Schema

Name	Required	Description	Default
`consignment`	Yes	Consignment data with complexItems array

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 / consignment / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

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

B3.3/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world, non-destructive write, so the safety profile is covered. The description adds only the distinctive payload trait (complexItems with packaging/DG data) and says nothing about creation side effects, whether a draft/pending consignment is produced, or carrier-dependent failures. No contradiction with annotations.

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 action and its differentiator in a single sentence, with no filler prose. The 'Args:' block is largely boilerplate that restates the only property, costing a little precision but not hurting readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a create operation taking one free-form nested object (schema is additionalProperties-only, so the '100% coverage' is misleading) with dangerous-goods payloads and an open-world annotation. The description gives no guidance on required consignment structure, valid complex item shapes, or where to discover the schema, which leaves an agent under-equipped for a genuinely complex tool. The presence of an output schema excuses it from explaining return values, but the input side remains thin.

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 nominally 100%, so the 3 baseline applies. The description does add one useful nugget the schema cannot express — that the consignment object must carry a complexItems array rather than standard items — but it does not describe the internal structure of those complex items or which other consignment fields are mandatory.

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 ('Creates a consignment') plus the distinguishing characteristic ('using complex item definitions ... instead of standard items'), which separates it conceptually from machship_create_consignment and machship_create_consignment_existing_items. It does not name those siblings, so the differentiation must be inferred from the parenthetical rather than stated.

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?

Implies the use case (when consignments need detailed packaging/dangerous goods data), which is a reasonable signal for choosing it over plain create_consignment. However, there is no explicit when-to-use/when-not and no named alternative, and no mention of prerequisites such as fetching a custom schema or consignment creation settings first.

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

Deploy Server