Spotinst MCP Server

by arnstarn

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_cluster_azure

Retrieve details of a specific Azure Ocean cluster, including configuration and status, using the cluster ID.

Instructions

Get details of a specific Azure Ocean cluster.

Args: cluster_id: The Ocean cluster ID (e.g. o-390ef886) account_id: Account ID for an Azure account.

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_azure"
  }
}

Input Schema

Name	Required	Description	Default
`cluster_id`	Yes
`account_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, required permissions, or error handling. The description is limited to the basic purpose, leaving the agent uninformed about side effects or constraints.

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 concise with two sentences plus an Args list, all front-loaded with the main purpose. No extraneous information is present, and the structure is clear, though it could be slightly more streamlined.

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?

Given the tool's simplicity (2 params, output schema present), the description covers the basics. However, it lacks information on expected outputs, error cases, or prerequisite conditions, which would improve completeness for an agent.

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

Parameters3/5

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

With 0% schema description coverage, the description adds meaning by explaining each parameter: cluster_id with an example (o-390ef886) and account_id as 'Account ID for an Azure account.' However, these descriptions are minimal and lack details on how to obtain or format the values.

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 explicitly states 'Get details of a specific Azure Ocean cluster,' which is a clear verb+resource pair. It distinguishes from sibling tools like list_clusters_azure and other get tools (e.g., get_cluster_costs) by specifying 'Azure Ocean cluster'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like get_cluster_costs or get_cluster_health. It only describes what it does, without any context on appropriate usage scenarios or exclusions.

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