machship-mcp

Get All Company Items

machship_get_items

Read-onlyIdempotent

Retrieves a paginated list of saved items for a specific company, with configurable start index and page size up to 200.

Instructions

Returns a paginated list of saved items for a company (max 200 per request).

Args:

companyId (number): Company ID
startIndex (number, optional): Pagination start index (default 1)
retrieveSize (number, optional): Number of items to retrieve (default 200, max 200)

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>"
    },
    "name": "machship_get_items"
  }
}

Input Schema

Name	Required	Description
`companyId`	Yes	Company ID
`startIndex`	No	Pagination start index
`retrieveSize`	No	Items to retrieve (max 200)

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.

Changed3 schema fields changedv1.0.1Nov 3, 2026

addedInput schema / properties / companyId / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / startIndex / 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

A3.5/5.0

Behavior3/5

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

The annotations already establish a read-only, idempotent, non-destructive external operation. The description adds useful pagination behavior and the 200-item request cap, but provides no further context such as result ordering or how to determine whether additional pages remain.

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 core purpose and page-size limit are front-loaded in a compact opening sentence. The argument list is readable but largely redundant with the input schema, preventing a top conciseness score.

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?

For a simple three-parameter read operation with complete input documentation, an output schema, and safety annotations, this is sufficient for basic invocation. Its main completeness gap is the lack of differentiation from closely related item tools, with pagination traversal guidance a secondary omission.

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%, so the baseline is 3. The Args section restates the parameter names, defaults, and maximum already present in the schema without adding meaning such as how companyId is obtained or how startIndex should advance between pages.

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 clearly states the verb, resource, and scope: returning a paginated list of saved items for a company. It does not distinguish this company-wide listing from siblings such as machship_get_items_complex, machship_get_items_by_skus, or machship_get_item.

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?

Company-scoped, paginated listing implies when the tool is useful, but there is no explicit selection guidance. Given the many closely related item-retrieval siblings, the description should explain when to use this simpler list operation instead of SKU-based, single-item, or complex-item alternatives.

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

Deploy Server