Spotinst MCP Server

Overview Schema Source Related Servers Discussions Admin

initiate_roll

Initiate a rolling restart of nodes in an Ocean cluster to drain and replace nodes in batches, requiring confirmation to prevent accidental rollouts.

Instructions

DESTRUCTIVE: Initiate a rolling restart of nodes in an Ocean cluster. This will drain and replace nodes in batches. Requires confirm=true.

Args: cluster_id: The Ocean cluster ID (e.g. o-abc12345) confirm: Must be true to execute. Safety guard against accidental rolls. batch_size_percentage: Percentage of nodes to roll per batch (default: 20) batch_min_healthy_percentage: Min healthy nodes per batch (default: 50) respect_pdb: Respect PodDisruptionBudgets (default: true) launch_spec_ids: Comma-separated VNG IDs to roll (e.g. ols-abc,ols-def). Empty = all. instance_ids: Comma-separated instance IDs to roll. Empty = all in scope. account_id: Optional account ID. Defaults to SPOTINST_ACCOUNT_ID env var. cloud: Cloud provider: aws or azure (default: aws)

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "initiate_roll"
  }
}

Input Schema

Name	Required	Default
`cluster_id`	Yes
`confirm`	No
`batch_size_percentage`	No
`batch_min_healthy_percentage`	No
`respect_pdb`	No
`launch_spec_ids`	No
`instance_ids`	No
`account_id`	No
`cloud`	No	aws

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description prominently labels the tool as 'DESTRUCTIVE' and explains the behavior (drain and replace nodes in batches). It also warns about accidental rolls with the confirm parameter. Without annotations, it carries the full burden and does so adequately, though it could mention if the action is synchronous or asynchronous.

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 description is well-structured with a clear warning and bullet-pointed arguments. It is somewhat lengthy but every sentence adds value. Minor redundancy (e.g., 'Requires confirm=true' could be part of the confirm description).

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?

Given no annotations, the description covers behavior, all parameters, and a safety warning. It does not discuss error conditions or prerequisites (e.g., permissions), but the output schema may handle return values. Overall comprehensive for initiating a roll.

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?

With 0% schema description coverage, the description fully compensates by explaining all 9 parameters: providing examples (e.g., cluster_id: 'o-abc12345'), clarifying the confirm guard, and stating defaults. This goes well beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Initiate a rolling restart'), the resource ('nodes in an Ocean cluster'), and the process ('drain and replace nodes in batches'). It distinguishes itself from siblings like get_roll or list_rolls by focusing on initiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use (for rolling restart), explicitly requires confirm=true as a safety guard, and mentions default values. However, it does not explicitly compare to alternatives like get_roll for monitoring or list_rolls for existing rolls, but the instructions are clear enough.

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