Skip to main content
Glama
Sign In
machship-mcp

machship-mcp

by devkindhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Attachments by Consignment IDs

machship_get_attachments_by_consignment_ids
Read-onlyIdempotent

Download attachments for up to 40 consignment IDs in one bulk ZIP, returning file content, type, and size for each response.

Instructions

Downloads attachments for up to 40 consignments in bulk (returned as zip). Returns { fileBase64, contentType, sizeBytes }. contentType comes from the response header.

Args:

  • ids (number[]): Array of consignment IDs (max 40)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ids": "<ids>"
    },
    "name": "machship_get_attachments_by_consignment_ids"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesConsignment IDs (max 40)

Output Schema

NameRequiredDescriptionDefault
errorsNoValidation errors returned by Machship, if any
objectNoResponse payload from the Machship API

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • addedInput schema / properties / ids / 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"
+}
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuine value with the zip packaging and the note that contentType is taken from the response header, but it omits what happens when some consignments have no attachments or when an ID is invalid, and says nothing about payload size for a 40-consignment zip.

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 operation and its constraint in one sentence, followed by the return shape, then the arguments. The 'Args' block is largely redundant with a fully documented schema, which is the only real waste.

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 bulk download the description covers scope, format and return keys, and an output schema exists so return values are already structural. Remaining gap is partial-failure/empty-attachment behavior, which is meaningful but not blocking.

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 'Args' block merely restates the schema ('ids (number[]): Array of consignment IDs (max 40)') including the same maxItems=40 constraint. No added meaning such as whether unknown/invalid IDs are ignored or cause failure, so baseline 3 applies.

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 ('Downloads attachments for up to 40 consignments in bulk') plus the output form (zip), which implicitly separates it from the single-record attachment siblings. It never names those siblings (e.g. machship_get_attachment, machship_get_consignment_attachments), so the agent must infer the split from the 'bulk / max 40' phrasing.

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?

Usage is only implied: 'in bulk' and the 40-item cap hint that this is the batched alternative to single-attachment fetching, but there is no explicit when-to-use or when-not-to-use statement and no alternative is named. An agent can guess correctly but is not guided.

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

Deploy Server

Other Tools