Skip to main content
Glama
Sign In
Spotinst MCP Server

Spotinst MCP Server

by arnstarn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_vng_azure

Retrieve details of an Azure Virtual Network Gateway by VNG ID and optional account ID.

Instructions

Get details of a specific Azure VNG.

Args: vng_id: The VNG ID (e.g. vng-14e08b61) 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": {
      "vng_id": "<vng_id>"
    },
    "name": "get_vng_azure"
  }
}

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

A3.5/5.0
Behavior2/5

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

No annotations exist, so description carries full burden. It only implies read-only by 'Get details' but doesn't explicitly state permissions, side effects, or return format. Minimal behavioral disclosure.

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?

Extremely concise: one sentence for purpose, two lines for args. No redundant words, front-loaded with essential info.

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?

Adequate for a simple get tool, but missing explicit mention that vng_id is required (implied by schema), and no error or usage context. Output schema exists but not referenced.

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%, but description adds value by providing examples (vng-14e08b61) and clarifying that account_id is an Azure account ID. Could note optionality of account_id.

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 it retrieves details of a specific Azure VNG, using strong verb-resource pairing. It distinguishes from siblings like list_vngs_azure (list all) and get_vng (likely for non-Azure).

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 guidance on when to use this tool vs alternatives like list_vngs_azure or get_vng. No when-not or context cues provided.

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