Skip to main content
Glama
Sign In
machship-mcp

machship-mcp

by devkindhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Company Items by SKUs (Batch)

machship_get_items_by_skus
Read-onlyIdempotent

Look up saved standard items by up to 100 SKU codes for a company, returning matching records so you can verify which SKUs exist; unmatched codes are omitted.

Instructions

Returns a list of saved items matching any of the supplied SKUs (standard items only, max 100 SKUs). SKUs that don't match any item are silently omitted — compare returned Sku values against your input to detect misses.

Args:

  • companyId (number): Company ID

  • skus (string[]): Array of SKU codes to look up (max 100)

Input Schema

NameRequiredDescriptionDefault
skusYesSKU codes to look up (max 100)
companyIdYesCompany 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 / 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"
+}
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world semantics. The description adds genuinely non-obvious behavior: unmatched SKUs are silently omitted rather than erroring, and the caller must diff returned Sku values against the input to detect misses. The 100-SKU cap and standard-items-only restriction are also disclosed. It does not state what happens on an empty result set versus an error.

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?

Front-loaded with the return behavior and the silent-omission caveat, which are the highest-value sentences. The trailing Args block duplicates schema text and could be dropped, but overall there is little wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain return shape, and it instead spends its space on the one thing the schema cannot convey: that misses are silent and how to detect them. For a two-parameter read tool this covers everything an agent needs to call it correctly.

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%, so baseline is 3, and the description adds match-any (OR) semantics for the skus array that the schema does not express. The inline Args block largely restates the schema's own descriptions of companyId and skus, providing little beyond the limit already encoded in maxItems.

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?

Specific verb and resource with scope qualifiers: batch lookup of 'saved items matching any of the supplied SKUs', restricted to 'standard items only'. The batch/any-of framing and the 'standard items only' restriction distinguish it reasonably from single-lookup siblings, though it never names machship_get_item_by_sku or machship_get_items_complex explicitly.

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?

The batch-with-max-100 nature implies when to prefer this over a single-SKU lookup, but that inference is left to the agent. There is no explicit guidance on when to use machship_get_item_by_sku, machship_get_items, or machship_get_items_complex instead, and no stated prerequisites beyond the required companyId.

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