machship-mcp

Group Consignments for Printing

machship_group_consignments_for_printing

Read-only

Groups consignment IDs for batch label printing and returns the resulting print groups.

Instructions

Groups consignments for batch label printing and returns print groups.

Args:

consignmentIds (number[]): Consignment IDs to group for printing

Input Schema

Name	Required	Description	Default
`consignmentIds`	Yes	Consignment IDs

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 / consignmentIds / 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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the output is 'print groups', but says nothing about whether the grouping is persisted, ordering, or how the groups are structured beyond what the output schema presumably shows.

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?

A single sentence stating purpose and return value, front-loaded and free of padding. The extra Args block is redundant with the already-complete schema but is short and does not obscure the main sentence.

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 one parameter, full schema coverage, an output schema, and annotations, the description covers enough to invoke the tool correctly. The only meaningful gap is disambiguation from the sibling grouping tools in this dense toolset.

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% and there is only one required parameter, so the schema already fully documents consignmentIds. The description's Args block merely restates it without adding format, batch limits, or grouping semantics beyond what the schema provides.

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 ('Groups consignments') plus the end goal ('batch label printing') and what it returns ('print groups'). It is not, however, distinguished from the very similar siblings machship_group_consignments_for_consolidation, machship_group_consignments_for_manifest, and machship_group_all_for_manifest.

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?

The phrase 'for batch label printing' hints at the use case but gives no explicit when-to-use guidance, no prerequisites, and no exclusions. With several near-identical grouping tools and label-retrieval tools like machship_get_consignment_label_pdf and machship_send_labels_to_printer in the sibling list, an agent is left to guess which one to call.

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

Deploy Server