Skip to main content
Glama
Sign In
machship-mcp

machship-mcp

by devkindhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Manifest / Book Consignments with Carrier

machship_manifest_consignments

Books consignments with the carrier to create pickup bookings and generate tracking numbers, completing the consignment workflow before physical pickup.

Instructions

Books/manifests consignments with the carrier — creates the pickup booking and generates tracking numbers. This is the final step in the consignment workflow before physical pickup.

Args:

  • manifests (array): Array of booked manifest objects with consignment IDs and carrier booking details

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": {
      "manifests": "<manifests>"
    },
    "name": "machship_manifest_consignments"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestsYesManifest booking objects (consignmentIds, carrierId, despatchDate, etc.)

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 / manifests / items / 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"
+}
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations’ external, non-idempotent mutation profile, the description discloses that the call creates a pickup booking and generates tracking numbers. It omits duplicate-booking, partial-failure, and retry behavior, but the concrete side effects provide useful additional context.

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 action and workflow position are front-loaded in two efficient sentences. The Args block is somewhat redundant with the schema, but the overall definition remains short and easy to scan.

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?

The output schema removes the need to document return values, and the description covers the operation’s basic role and effects. However, the free-form manifest item objects, lack of payload-construction guidance, and absence of routing to grouping or rebooking siblings leave gaps for reliable invocation.

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?

The manifests argument is described in both the description and fully covered schema, and the description adds little beyond “consignment IDs and carrier booking details.” With 100% schema coverage the baseline is 3; neither source defines the item object’s required fields or formats.

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 opening line gives a specific verb and resource—“Books/manifests consignments with the carrier”—and adds concrete outcomes. It does not distinguish this operation from siblings such as machship_rebook_manifest_pickup or the manifest-grouping tools, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

“This is the final step in the consignment workflow before physical pickup” supplies clear sequencing and when-to-use context. It does not state prerequisites, when not to use it, or which sibling to use for grouping or rebooking.

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