skypilot-mcp

skypilot_cluster_stop

Destructive

Stop a running cloud cluster to halt instance billing while preserving attached disk data. Enable graceful mode to let in-progress uploads finish and prevent data loss.

Instructions

Stop a running cluster. Data on attached disks is preserved. Billing for instances stops but disk charges continue. Set graceful=True to wait for in-progress data uploads to finish before stopping (prevents data loss). Returns a request_id.

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_name": "<cluster_name>"
    },
    "name": "skypilot_cluster_stop"
  }
}

Input Schema

Name	Required	Description	Default
`purge`	No
`graceful`	No
`cluster_name`	Yes
`graceful_timeout`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The description adds substantial behavioral context beyond the destructiveHint annotation: it explains billing implications ('billing for instances stops but disk charges continue'), data preservation on attached disks, what graceful=True does, and that a request_id is returned. It does not, however, explain the purge parameter's effect, which is a notable omission for a destructive-adjacent operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences, front-loaded with the core action, then side effects, a key parameter tip, and the return value. Every sentence adds value and there is no redundancy.

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?

An output schema exists and annotations cover the destructive hint, so the description need not explain return values. However, it is incomplete for a 4-parameter stop tool because it omits purge and graceful_timeout semantics, and its blanket claim that 'data on attached disks is preserved' may be misleading if purge is set.

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

Parameters2/5

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

With 0% schema description coverage, the description must carry parameter semantics. It explains only graceful; it does not mention purge (which is likely destructive) or graceful_timeout, leaving three of four parameters undocumented. This is a significant gap given the low schema coverage.

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 states a clear verb and resource: 'Stop a running cluster.' It is unambiguous and specific. However, it does not explicitly differentiate from siblings like skypilot_cluster_down or skypilot_cluster_autostop, which would help an agent choose correctly.

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?

Usage is implied by 'Stop a running cluster,' and the graceful tip provides some context for when to use that parameter. But there is no explicit guidance on when to prefer this over cluster_down, autostop, or api_stop, and no exclusions or prerequisites are stated.

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

Deploy Server