Spotinst MCP Server

Overview Schema Source Related Servers Discussions Admin

list_elastigroups

List all Elastigroups in a Spotinst account with compact summaries or full configurations for detailed analysis.

Instructions

List all Elastigroups in a Spotinst account. Returns compact summaries by default (id, name, region, capacity). Set verbose=true for full Elastigroup configs (compute, networking, scaling).

Args: account_id: Optional account ID to query. Defaults to SPOTINST_ACCOUNT_ID env var. verbose: Return full configurations instead of compact summaries (default: false). Use when analyzing Elastigroup settings, troubleshooting, or comparing configs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_elastigroups"
  }
}

Input Schema

Name	Required	Description	Default
`account_id`	No
`verbose`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.4.0Apr 30, 2026

addedInput schema / properties / verbose

Added value: +{
+  "default": false,
+  "title": "Verbose",
+  "type": "boolean"
+}

First observedv0.1.0Mar 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description fully discloses behavior: returns compact summaries by default, full configs with verbose=true. It explains the output modes and parameter effects. Missing details on pagination or limits, but acceptable for a list operation with two parameters.

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 efficiently structured: a concise opening sentence, followed by clear bullet-point style for output modes, and a structured Args section. Every sentence adds value without 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 input parameters, default behavior, and output variations. It is sufficient for a list tool with two parameters and an output schema. However, it does not mention pagination or limits, and could explicitly reference sibling tools for singular retrieval (get_elastigroup) for complete context.

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, so the description compensates fully. It explains that account_id is optional and defaults to an environment variable, and verbose returns full configurations with specific use cases. This adds significant meaning beyond the schema's bare types and defaults.

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 'List all Elastigroups in a Spotinst account' with specific verb and resource. It distinguishes between compact summaries and full configurations via the verbose parameter, and contrasts with sibling tools like get_elastigroup (singular) through implication.

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 provides guidance on when to use verbose=true ('analyzing Elastigroup settings, troubleshooting, or comparing configs'). However, it lacks explicit differentiation from sibling tools like get_elastigroup (for a single group) or list_accounts, and does not state when not to use this tool.

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