Skip to main content
Glama
Sign In
machship-mcp

machship-mcp

by devkindhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Quote with Complex Items

machship_create_quote_complex_items

Creates a freight quote for items needing detailed packaging, dangerous goods codes, serial numbers, or non-standard definitions that standard quote requests cannot handle.

Instructions

Creates a freight quote using complex item definitions (detailed packaging, dangerous goods, serialisation data).

Args:

  • quote (object): Quote request with complexItems array instead of standard items

Returns: Same as machship_create_quote — array of rate options with cost and transit info.

Examples:

  • Use when: Items have dangerous goods codes, serial numbers, or non-standard packaging

  • Use when: machship_create_quote returned a validation error about item structure

Input Schema

NameRequiredDescriptionDefault
quoteYesQuote request with complexItems array

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

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the mutation and external-carrier profile is known. The description's main addition is the return shape ("array of rate options with cost and transit info"), which is partly redundant given an output schema exists, and it says nothing about auth, rate limits, or whether quote calls are billable/committal. Adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded one-line purpose followed by compact Args/Returns/Examples blocks. Every line carries information an agent needs; no filler or restatement of the tool name.

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?

Output schema and annotations cover return values and safety, and the description links behavior back to machship_create_quote. The one remaining gap is that the internal shape of complexItems is undefined in both schema and description, though the usage triggers and sibling references mitigate this.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but the schema itself is a bare object with additionalProperties, so the description genuinely adds meaning: the payload must carry a complexItems array 'instead of standard items', which is the key structural difference from machship_create_quote. It does not enumerate the complexItems fields, so 4 rather than 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Creates a freight quote") and immediately narrows scope with "using complex item definitions (detailed packaging, dangerous goods, serialisation data)". This makes it distinguishable from the sibling machship_create_quote and from get_routes_complex_items without opening a schema.

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

Usage Guidelines5/5

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

Two explicit 'Use when' triggers are given: items with DG codes/serials/non-standard packaging, and specifically falling back here after machship_create_quote returns an item-structure validation error. That names both the condition and the alternative tool, leaving nothing to inference.

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