Skip to main content
Glama
Sign In
machship-mcp

machship-mcp

by devkindhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Available Routes with Complex Items

machship_get_routes_complex_items
Read-only

Retrieve available freight routes for shipments containing dangerous goods or specialised packaging, using complex item definitions to return carrier options that match your shipment requirements.

Instructions

Returns available routes for a shipment with complex item definitions (dangerous goods, specialised packaging).

Args:

  • request (object): Route request with complexItems array (including dangerous goods classifications)

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": {
      "request": "<request>"
    },
    "name": "machship_get_routes_complex_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesRoute request with complexItems (dangerous goods, specialised packaging)

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description's contribution is clarifying what 'complex items' means (dangerous goods classifications, specialised packaging), but it says nothing about validation failures, carrier availability behavior, or why idempotentHint is false for a read.

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?

Two short, front-loaded statements with no filler; the core purpose comes first. The 'Args:' block duplicates what the schema already documents, which is slight waste but not harmful.

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?

Output schema and annotations are present, so return values and safety need not be explained. However, for a tool whose only differentiator is 'complex items' versus two sibling route tools, the description omits the selection guidance an agent most needs.

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 there is a single required 'request' object, so the schema already documents the parameter and its nested complexItems content. The description restates the same thing and adds only a marginal note about dangerous goods classifications, 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 ('Returns available routes') and qualifies the input shape ('shipment with complex item definitions'), which distinguishes it from the plain routes tools in spirit. It does not explicitly name machship_get_routes or machship_get_routes_batch as the non-complex alternatives, so the agent must infer the boundary.

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: an agent can infer this is for shipments containing dangerous goods or specialised packaging, but there is no explicit 'use this instead of X when Y' or statement of prerequisites. With two closely named siblings (get_routes, get_routes_batch) present, an explicit routing rule would be expected.

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