Spotinst MCP Server

Overview Schema Source Related Servers Discussions Admin

get_cluster_scheduling

Retrieve scheduling and auto-scaler configuration for an Ocean cluster, including shutdown hours, scheduled tasks, and auto-scaler settings.

Instructions

Get scheduling and auto-scaler configuration for an Ocean cluster (AWS or Azure). Shows shutdown hours, scheduled tasks, and auto-scaler settings.

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": "get_cluster_scheduling"
  }
}

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/5.0

Behavior3/5

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

With no annotations, description carries full burden. It implies a read operation ('Get configuration'), but doesn't disclose permissions, rate limits, or error behavior (e.g., missing cluster). Adequate but not comprehensive.

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?

Concise: overview sentence then parameter docs in standard format. No unnecessary phrases. Front-loaded with purpose.

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 3 parameters and output schema existence, description covers what the tool returns (shutdown hours, tasks, settings). Could mention output structure more, but output schema is available.

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

Parameters4/5

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

Schema has 0% description coverage, but description adds meaningful detail: cluster_id example, account_id explanation with env var, cloud options. Good compensation for missing schema descriptions.

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?

Description clearly states 'Get scheduling and auto-scaler configuration for an Ocean cluster (AWS or Azure).' It specifies the action (get), resource (cluster scheduling config), and scope, distinguishing it from sibling tools like get_cluster or get_cluster_health.

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?

No explicit when-to-use or when-not-to-use guidance. While the purpose is clear, it doesn't provide context for when this tool should be chosen over alternatives like get_cluster or list_clusters.

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