Spotinst MCP Server

Overview Schema Source Related Servers Discussions Admin

get_elastigroup

Retrieve details of a specific Elastigroup using its group ID. Optionally, specify an account ID to query a particular account.

Instructions

Get details of a specific Elastigroup.

Args: group_id: The Elastigroup ID (e.g. sig-abc12345) account_id: Optional account ID to query. Defaults to SPOTINST_ACCOUNT_ID env var.

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": {
      "group_id": "<group_id>"
    },
    "name": "get_elastigroup"
  }
}

Input Schema

Name	Required	Description	Default
`group_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

A3.8/5.0

Behavior3/5

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

The 'get' verb implies read-only, but no annotations are provided to confirm. The description lacks explicit mention of side effects, idempotency, or error handling. Acceptable but minimal transparency.

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?

Two sentences plus parameter list, no fluff. Front-loaded purpose, efficient and structured.

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?

Covers purpose and parameters well. Output schema exists, so return documentation is not needed. Lacks error or edge case behavior, but acceptable for a simple retrieval tool.

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?

Both parameters are described with examples and default behavior (e.g., 'e.g. sig-abc12345' for group_id, 'Defaults to SPOTINST_ACCOUNT_ID env var' for account_id). Adds significant value over zero 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?

Clearly states 'Get details of a specific Elastigroup', providing a specific verb and resource. Distinguishes from siblings like list_elastigroups which lists all groups.

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?

No explicit guidance on when to use this tool versus alternatives. Does not mention when not to use or suggest sibling tools like list_elastigroups for listing all groups.

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