machship-mcp

Get Consignment Attachments

machship_get_consignment_attachments

Read-onlyIdempotent

Retrieve attachment metadata for a Machship consignment by ID, listing available files without downloading their contents.

Instructions

Returns attachment metadata (not file contents) for a consignment.

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

A3.7/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, and the description adds a meaningful nuance beyond them: the response contains attachment metadata only, not file contents. It says nothing about permissions, rate limits, or what happens when a consignment has no attachments, but the core behavioral distinction is present.

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 two-line description is front-loaded and efficient, with the important metadata-not-contents caveat in the first sentence. The Args block merely restates the schema and is slightly redundant, but it costs little space.

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?

For a single-parameter read tool with full annotations and an output schema, the description covers the essential scope and return-content distinction. Minor omissions such as behavior for consignments without attachments are acceptable given the structured metadata available.

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?

There is only one parameter and the schema already documents it at 100% coverage with the same 'Consignment ID' wording, so the description adds no semantic detail. The baseline of 3 applies when the schema fully carries parameter meaning.

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 ('Returns') and resource ('attachment metadata') scoped to a single consignment, and clarifies it excludes file contents, which helps separate it from attachment-content tools. It does not explicitly name the closest siblings such as machship_get_attachments_by_consignment_ids or machship_get_attachment, so it falls short of full sibling differentiation.

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?

The 'metadata (not file contents)' phrasing implies when this tool is appropriate versus retrieving actual files, but no sibling is named and no explicit when-not guidance is given. An agent must infer the choice against machship_get_attachment and machship_get_attachments_by_consignment_ids.

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

Deploy Server