Skip to main content
Glama
Sign In
machship-mcp

machship-mcp

by devkindhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Manifest PDF File Info

machship_get_manifest_pdf_file_info
Read-onlyIdempotent

Retrieve a manifest PDF as JSON using its manifest ID, including base64 file content, file name, and content type for download or storage.

Instructions

Returns the manifest PDF as JSON. object.content holds the file as base64, with object.fileName and object.contentType.

Args:

  • manifestId (number): Manifest ID

Input Schema

NameRequiredDescriptionDefault
manifestIdYesManifest ID

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 / manifestId / 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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful encoding detail (base64 content plus fileName and contentType), though with an output schema present this is somewhat redundant. No auth requirements, size limits, or error behavior are mentioned.

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 description is short and front-loads the return format. The Args section duplicates the schema but is compact; no sentence is wasteful, though it could be trimmed further.

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?

For a one-parameter read tool with annotations and an output schema, the description covers the essentials. The main gap is sibling differentiation: it does not clarify when to choose this base64 JSON variant over the raw manifest PDF tools, which is important given the crowded sibling set.

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 single manifestId parameter is fully documented in the schema. The description's 'manifestId (number): Manifest ID' restates the schema without adding format, validation, or sourcing guidance, 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?

The description states a specific verb and resource ('Returns the manifest PDF as JSON') and explains the payload shape (base64 content, fileName, contentType). It is clear what the tool produces, but it does not distinguish itself from siblings such as machship_get_manifest_label_pdf or machship_get_consignment_pdf_file_info, leaving ambiguity about which 'manifest PDF' this refers to.

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 guidance on when to use this tool versus the direct PDF-returning siblings. An agent must infer that this is the JSON/base64 variant rather than the raw PDF variant. No prerequisites, exclusions, or alternative tools are named.

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