Skip to main content
Glama
Sign In
Spotinst MCP Server

Spotinst MCP Server

by arnstarn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_vng

Get details of an AWS VNG (launch spec) by providing its ID and optional account ID.

Instructions

Get details of a specific AWS VNG (launch spec).

Args: vng_id: The VNG/launch spec ID (e.g. ols-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": {
      "vng_id": "<vng_id>"
    },
    "name": "get_vng"
  }
}

Input Schema

NameRequiredDescriptionDefault
vng_idYes
account_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It correctly implies a read-only operation (get details) but does not explicitly state safety or side effects. The absence of contradictions is noted.

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 followed by bullet-like parameter explanations. No fluff, and the most important information (what the tool does) is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of an output schema (handling return value details) and only two parameters, the description sufficiently covers the input semantics. No missing information for correct invocation.

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 coverage is 0%, so the description adds critical meaning: provides an example for vng_id and explains the default behavior of account_id. This goes beyond the bare schema.

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 'Get details of a specific AWS VNG (launch spec)', using a specific verb and resource. It distinguishes from sibling tools like list_vngs (list all) and create_vng/delete_vng/update_vng (mutations).

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 context is clear: use this tool when you have a VNG ID and want its details. However, it does not explicitly state when not to use it or mention alternatives, which would be helpful for disambiguation among sibling tools like get_vng_azure.

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

Deploy Server

Other Tools