machship-mcp

Get Consignment Label PDF

machship_get_consignment_label_pdf

Read-onlyIdempotent

Retrieve a consignment label as a PDF using its consignment ID, returning the file in Base64 with content type and size for printing or recordkeeping.

Instructions

Returns the consignment label PDF. Returns { fileBase64, contentType, sizeBytes }. contentType comes from the response header.

Args:

consignmentId (number): Consignment ID

Input Schema

Name	Required	Description	Default
`consignmentId`	Yes	Consignment ID

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 / consignmentId / 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 readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds one useful operational detail (contentType comes from the response header) but says nothing about failure modes such as labels not yet generated or consignment not manifested.

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 core statement and short overall, but the explicit return-field listing and the Args block largely duplicate the output schema and input schema, adding length without new meaning.

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 one parameter, an output schema, and rich annotations, only modest description content is required, and the return shape plus header caveat are covered. It still omits availability timing and any routing guidance among the many label/PDF siblings, which is the main gap.

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 the description's 'consignmentId (number): Consignment ID' merely restates the schema. It adds no format hints, no source of the ID, and no note that the schema types it as an integer rather than a number.

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: 'Returns the consignment label PDF', which an agent can immediately map to a label-retrieval action. It does not distinguish itself from close siblings such as machship_get_consignment_pdf_file_info or machship_get_item_label_pdf, so the caller must infer the difference.

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 description gives no when-to-use or when-not-to-use guidance and never names an alternative such as the file-info or PDF-file-info variants. The agent is left to guess whether this fetches bytes, metadata, or both.

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

Deploy Server