Spotinst MCP Server

Overview Schema Source Related Servers Discussions Admin

update_vng_azure

Update an Azure VNG configuration by providing its ID and a JSON string of fields to update. Requires explicit confirmation to execute changes.

Instructions

DESTRUCTIVE: Update an Azure VNG configuration. Requires confirm=true. Pass updates as a JSON string.

Args: vng_id: The VNG ID (e.g. vng-14e08b61) updates_json: JSON string of fields to update confirm: Must be true to execute. Safety guard. 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>",
      "updates_json": "<updates_json>"
    },
    "name": "update_vng_azure"
  }
}

Input Schema

Name	Required	Description	Default
`vng_id`	Yes
`updates_json`	Yes
`confirm`	No
`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.9/5.0

Behavior2/5

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

Discloses 'DESTRUCTIVE' nature and confirm guard, which is good given no annotations. But lacks details on permissions, side effects, error handling, or output behavior. The burden is fully on description, yet it only provides minimal safety context.

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?

Highly concise: 5 lines with clear front-loading of 'DESTRUCTIVE'. Every sentence serves a purpose without redundancy. Easy to parse quickly.

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, parameter semantics, and safety, but lacks details on updates_json structure and error conditions. With an output schema, return values are not needed, but some behavioral context is missing.

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?

With 0% schema description coverage, the description adds significant meaning: vng_id format example, updates_json as JSON string, confirm as safety guard requiring true, and account_id for Azure account. All parameters are explained effectively.

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 verb 'Update' and resource 'Azure VNG', distinguishing from siblings like delete_vng, create_vng, and update_vng (non-Azure). The 'DESTRUCTIVE' prefix and specific parameter mentions reinforce purpose.

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

Usage Guidelines3/5

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

Implied usage for updating Azure VNG configurations, with safety guard (confirm=true) and parameter requirements. However, no explicit guidance on when to use vs. alternatives or when not to use, leaving it to inference.

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