machship-mcp

Get Identities

machship_get_identities

Read-onlyIdempotent

Retrieve all identities owned by a Machship organisation, including linked companies, with optional filters for unlinked identities or identity provider. Requires administrator access.

Instructions

Get all identities owned by an organisation, with details on which companies they are linked to. Requires administrator access to the organisation.

Args:

organisationId (number): Organisation ID
onlyUnlinkedIdentities (boolean, optional): Return only identities not linked to any company
identityProviderId (number, optional): Filter by identity provider

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": {
      "organisationId": "<organisationId>"
    },
    "name": "machship_get_identities"
  }
}

Input Schema

Name	Required	Description
`organisationId`	Yes	Organisation ID
`identityProviderId`	No	Filter by identity provider ID
`onlyUnlinkedIdentities`	No	Return only unlinked identities

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 / identityProviderId / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / organisationId / 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 openWorld, so the safety profile is covered. The description contributes beyond that with the administrator-access requirement and a statement of what the response contains (identities plus company linkage). It says nothing about pagination or result size, which is a minor gap for a list endpoint.

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 description is two tight sentences with the purpose front-loaded and the permission caveat immediately after. The trailing Args block duplicates the fully-documented schema and is the only wasted space.

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 read-only, three-parameter list tool with a full output schema, the definition covers purpose, access requirements and filtering intent. Only return-shape nuances like paging or ordering are absent, which is acceptable given the output schema exists.

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 block largely restates the schema, though 'Return only identities not linked to any company' clarifies the boolean's intent slightly better than 'Return only unlinked identities'. No format or ID-source hints 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?

States a specific verb and resource with scope: 'Get all identities owned by an organisation, with details on which companies they are linked to.' The plural 'all' implicitly separates it from the singular machship_get_identity sibling, but no sibling is named 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?

Adds a real prerequisite ('Requires administrator access to the organisation'), which helps an agent decide whether it can call this at all. However, it never contrasts with adjacent tools such as machship_get_identity for a single record or machship_get_organisation_links, so the when-to-choose guidance is only implied.

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

Deploy Server