machship-mcp

Perform Consolidation

machship_perform_consolidation

Consolidates multiple consignments into fewer shipment units, merging them into consolidated shipments to improve carrier efficiency and reduce handling.

Instructions

Consolidates a set of consignments into consolidated shipments. This merges multiple consignments into fewer shipment units for carrier efficiency.

Args:

request (object): Consolidation request with consignment IDs and consolidation parameters

Input Schema

Name	Required	Description	Default
`request`	Yes	Consolidation request payload

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 / request / 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.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so safety and repeat-call behavior are covered. The description adds the useful semantic that multiple consignments collapse into fewer shipment units, but does not say what happens to the original consignments (consumed, linked, voided) or whether the operation is reversible, which matters for a non-idempotent mutation.

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?

Two tight sentences front-load the action and its effect, followed by a short Args note. The Args line largely restates the schema and could be trimmed, but there is no padding or redundancy elsewhere.

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 non-idempotent, open-world mutation with a nested request object, yet the description omits preconditions, ordering relative to the grouping tools, and the fate of source consignments. An output schema exists so return values need not be explained, but the missing workflow and side-effect context is a real gap for an agent deciding whether to call it.

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%, but the schema is effectively opaque ('Consolidation request payload' with additionalProperties {}), so the description's hint that the request contains consignment IDs and consolidation parameters is genuinely additive. However, it gives no field names, formats, or which consolidation parameters exist, so it only partially compensates for the loose schema.

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: 'Consolidates a set of consignments into consolidated shipments', plus a one-line rationale about merging into fewer shipment units. It is clear what the tool does, but it never distinguishes itself from the near-identical sibling machship_group_and_perform_consolidation or from machship_group_consignments_for_consolidation.

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 statement of when to use this versus the two consolidation-related siblings, no mention of prerequisites (e.g. whether consignments must first be grouped via machship_group_consignments_for_consolidation), and no exclusions. The agent must infer the workflow entirely from sibling names.

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

Deploy Server