machship-mcp

Get All Complex Company Items

machship_get_items_complex

Read-onlyIdempotent

Retrieve a paginated list of complex items for a specified company, using start index and page size controls capped at 200 items per request.

Instructions

Returns a paginated list of complex 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_complex"
  }
}

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.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely new operational facts not in the annotations: a hard 200-item cap per request and the pagination scheme's existence. It stops short of stating what an agent should do when a company exceeds 200 items (loop until a short page?) or any rate-limit behavior.

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 lead sentence is front-loaded with the verb, resource, scope, and cap, which is exactly what an agent needs first. The Args block is largely redundant with the structured schema, which is wasted space, though it does not obscure the core statement.

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?

An output schema exists and annotations are rich, so the description does not need to explain return shapes. For a simple three-parameter list tool it is close to sufficient; the main remaining gap is that 'complex item' is domain jargon left undefined and there is no guidance on paging through results when the total exceeds the 200 cap.

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 schema already documents companyId, startIndex, and retrieveSize including defaults and the max of 200. The Args block restates those descriptions nearly verbatim and adds no new meaning such as valid ranges, index base semantics beyond the default, or ordering of results. 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 a paginated list of complex items') scoped to a company, which implicitly separates it from the plain machship_get_items sibling and from the single-item machship_get_item_complex. It never names those siblings explicitly, so differentiation relies on the reader knowing what 'complex items' means in this domain.

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 paginated-list framing implies the use case (enumerate all complex items for a company), but there is no explicit when-to-use/when-not guidance and no mention of when to prefer machship_get_item_complex, machship_get_items_complex_by_sku-style lookups, or machship_get_items. Guidance is inferable rather than stated.

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

Deploy Server