machship-mcp

Group Consignments for Manifest

machship_group_consignments_for_manifest

Read-only

Group consignments into manifest groups to preview grouping before manifesting.

Instructions

Groups a specific set of consignments into manifest groups (preview before manifesting).

Args:

consignmentIds (number[]): Consignment IDs to group

Input Schema

Name	Required	Description	Default
`consignmentIds`	Yes	Consignment IDs to group

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.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; 'preview' is consistent with that and adds a little confirmation. The description does not address idempotentHint=false (whether repeated calls with the same IDs produce different groupings) or what grouping state, if any, is returned or persisted — the notable remaining gap.

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 core sentence is front-loaded and the parenthetical preview note is well placed. The 'Args:' section is pure repetition of the schema and could be dropped, but overall it is short and readable.

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?

With an output schema present, return values need no explanation, and the single parameter is documented. What is missing for a workflow-oriented grouping tool is the state model: whether the grouping is ephemeral preview data or persisted, and what the agent should do with the result before calling the manifest tool.

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 the single parameter is fully typed with minItems, so the schema carries the load. The description's 'Args' block restates the schema text verbatim and adds no meaning about ordering, duplicate IDs, or cross-company constraints.

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?

The description names a specific verb and resource ('Groups a specific set of consignments into manifest groups') and adds a scope qualifier ('specific set'), which implicitly separates it from machship_group_all_for_manifest. It stops short of naming any sibling outright, so an agent must infer the boundary from the word 'specific'.

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?

'preview before manifesting' tells the agent this is a pre-step in the manifest workflow, which is useful context. However, it never states when to choose this over machship_group_all_for_manifest, machship_group_and_perform_consolidation, or machship_manifest_consignments, and gives no prerequisites or exclusions.

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

Deploy Server