machship-mcp

Get Company Item by SKU

machship_get_item_by_sku

Read-onlyIdempotent

Retrieve a saved Machship item by its SKU code and company ID so you can look up product details needed for quoting, shipment creation, or carrier management.

Instructions

Returns a saved item matching the given SKU for a company.

Args:

companyId (number): Company ID
sku (string): Product SKU code

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": {
      "companyId": "<companyId>",
      "sku": "<sku>"
    },
    "name": "machship_get_item_by_sku"
  }
}

Input Schema

Name	Required	Description	Default
`sku`	Yes	Product SKU
`companyId`	Yes	Company ID

Output Schema

Name	Required	Description	Default
`errors`	No	Validation errors returned by Machship, if any
`object`	No	Response payload from the Machship API

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.1Nov 3, 2026

addedInput schema / properties / companyId / 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"
+}

First observedv1.0.0Jun 12, 2026

TDQS

B3.2/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 and openWorldHint=true, so the safety and repeatability profile is fully covered. The description adds only that the item is "saved" and scoped to a company; it says nothing about what happens when no SKU matches (empty result vs error) or about authentication scope, which would be the meaningful additions here.

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 first sentence is front-loaded and earns its place, and the Args block is short. It is mildly redundant with the schema, but nothing is padded or confusing.

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 simple two-parameter getter with an output schema and full annotations, the description is adequate — the response shape need not be explained. What's missing is the not-found behavior and any routing hint among the many item-lookup siblings, which matter given how crowded that namespace is.

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 description's Args block simply restates the parameter names, types and one-line meanings already present in the schema. Baseline 3 applies since the schema does all the work and no extra semantics (format of SKU, companyId provenance) are added.

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 gives a specific verb and resource ("Returns a saved item") plus the lookup key and scope ("matching the given SKU for a company"), which is clear on its own. However, it never differentiates itself from the many close siblings — machship_get_items_by_skus (batch), machship_get_item_complex_by_sku, or machship_get_item — so an agent must infer that this is the single, simple item lookup.

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 when-to-use guidance, no stated exclusions, and no reference to alternatives. The description doesn't say whether to prefer this over get_item_complex_by_sku when richer item data is needed, or over get_items_by_skus when multiple SKUs are involved.

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

Deploy Server