Google Cloud MCP Server

Delete Compute Instance

gcp-compute-delete-instance

Delete a Google Compute Engine VM instance by specifying its name and zone. Removes the instance to help manage compute resources.

Instructions

Delete a Compute Engine VM instance by name and 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": {
      "name": "<name>",
      "zone": "<zone>"
    },
    "name": "gcp-compute-delete-instance"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Instance name
`zone`	Yes	Zone of the instance (e.g., us-central1-a)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Sep 6, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool deletes an instance but does not disclose that deletion is destructive/irreversible, may require specific IAM permissions, or that stopping the instance first may be required in some workflows.

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 a single, front-loaded sentence with no filler. It conveys the action and the required identifying information efficiently, making it easy for an agent to parse.

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 tool is simple with only two parameters, and the description covers the essential invocation details. However, with no annotations and no output schema, it omits behavioral warnings expected for a destructive operation, such as irreversibility or permission requirements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with both 'name' and 'zone' already documented in the input schema. The description adds no extra meaning beyond what the schema provides, so it meets the baseline but does not exceed it.

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 states a specific verb ('Delete'), a specific resource ('Compute Engine VM instance'), and the required scope ('by name and zone'). This clearly distinguishes it from siblings like gcp-compute-create-instance, gcp-compute-start-instance, and gcp-compute-stop-instance.

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 description provides clear context: this tool is for deleting a specific VM when you know its name and zone. It does not explicitly name alternatives or when-not-to-use scenarios, but the operation is specific enough that an agent can readily select it.

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

Deploy Server