machship-mcp

Reset Organisation Public Key

machship_reset_organisation_public_key

Resets an organisation's public key by generating a new one without affecting existing links.

Instructions

Resets the public key for an organisation (generates new key). Does NOT affect existing links.

Args:

id (number, optional): Organisation ID (defaults to current org)

Input Schema

Name	Required	Description	Default
`id`	No	Organisation ID (optional)

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

Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false; the description adds real context beyond them by explaining that a new key is generated and that existing organisation links are unaffected, which bounds the blast radius. It still doesn't say whether the previous key is immediately invalidated.

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 prose is two tight, front-loaded sentences with the key scope caveat up front. The repeated 'Args:' block largely duplicates the fully documented schema, which is minor waste.

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?

Output schema exists so return values need no explanation, and impact on links is covered. However, for a key-rotation mutation the description omits whether the old key stops working and whether elevated permissions are required, which are the operationally critical facts.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is already typed, but the description adds the meaningful default behavior ('defaults to current org') that the schema's 'Organisation ID (optional)' does not convey, so the agent knows it can call with no arguments.

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 concrete verb+resource ('Resets the public key for an organisation') and clarifies the effect with '(generates new key)', which separates it from the read-only sibling machship_get_organisation_public_key. It stops short of naming the sibling alternatives 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?

There is a partial exclusion ('Does NOT affect existing links') that tells the agent this is not a link-management tool, but no positive guidance on when to reset versus merely reading the key with get_organisation_public_key, and no stated prerequisites or permissions.

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

Deploy Server