Scaleway MCP Server

delete_instance

Delete a Scaleway instance by its ID, with optional zone specification. Removes the instance from your infrastructure.

Instructions

Delete an instance.

Args: instance_id: The ID of the instance to delete zone: Scaleway zone (e.g., fr-par-1). If not provided, uses default zone.

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": {
      "instance_id": "<instance_id>"
    },
    "name": "delete_instance"
  }
}

Input Schema

Name	Required	Description	Default
`zone`	No
`instance_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits, but it only says 'Delete an instance' and lists parameters. It does not mention permanence, irreversibility, or potential impact on associated resources, which are critical for a destructive operation.

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 brief and structured with an Args section, making it easy to scan. Each sentence earns its place and there is no filler or redundancy.

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?

The description covers parameter meanings and the zone default, and an output schema exists so return values need no explanation. However, it misses important contextual details for a delete tool, such as irreversibility or failure scenarios, making it only partially complete.

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 description coverage is 0%, but the description fully defines both parameters. instance_id is explained as 'The ID of the instance to delete', and zone provides an example ('fr-par-1') and explains default behavior ('If not provided, uses default zone'), adding value beyond the 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 explicitly states 'Delete an instance', a specific verb-resource pair that clearly identifies the tool's function. It distinguishes itself from sibling tools like get_instance, start_instance, and stop_instance by the unique delete action.

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?

The description gives no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., instance should be stopped) or situations where deletion might be inappropriate. Usage is only implied by the verb 'delete'.

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

Deploy Server