Spotinst MCP Server

by arnstarn

Overview Schema Source Related Servers Discussions Admin

Python

Remote

export_cluster_yaml

Export an Ocean cluster configuration as YAML for GitOps comparison or backup.

Instructions

Export an Ocean cluster configuration as YAML. Useful for GitOps comparison or backup.

Args: cluster_id: The Ocean cluster ID (e.g. o-abc12345) account_id: Optional account ID to query. 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": "export_cluster_yaml"
  }
}

Input Schema

Name	Required	Default
`cluster_id`	Yes
`account_id`	No
`cloud`	No	aws

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.0Apr 30, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations, the description should disclose safety and behavior. It explains parameter defaults (account_id env var, cloud defaults to aws) but does not state whether the operation is read-only, idempotent, or what happens on invalid input.

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 concise: one sentence for purpose, then a clean Args section with clear parameter explanations. Every sentence adds value, no redundancy.

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?

The description covers purpose, parameters, and use case. Since an output schema exists, detailed return value documentation is not needed. However, it lacks information about error handling or edge cases.

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 has 0% description coverage, but the description adds valuable meaning: example for cluster_id ('e.g. o-abc12345'), explains account_id fallback to environment variable, and lists valid cloud providers ('aws or azure'). This significantly compensates for the schema gap.

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 ('Export') and the resource ('Ocean cluster configuration as YAML'), with a specific use case ('GitOps comparison or backup'). This distinguishes it from sibling tools like get_cluster which likely return JSON.

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 mentions specific use cases ('GitOps comparison or backup') but does not explicitly exclude alternatives or provide when-not-to-use guidance. It implies usage context well.

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