Google Cloud MCP Server

Get Compute VM Status

get-compute-vm-status

Check a Compute Engine VM's status by providing zone and VM name. Use this to find whether an instance is running, stopped, or in another state.

Instructions

Retrieve the status of a Compute Engine VM instance

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": {
      "zone": "<zone>",
      "vmName": "<vmName>"
    },
    "name": "get-compute-vm-status"
  }
}

Input Schema

Name	Required	Description
`zone`	Yes	Zone of the instance (e.g., us-central1-a)
`vmName`	Yes	VM name
`projectId`	No	Project ID (optional, will use default if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Sep 6, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden. 'Retrieve' implies a read-only operation, but the description does not disclose what statuses are returned, whether the VM must exist first, permission requirements, or behavior on errors. This is minimal transparency for a tool with no annotation safety hints.

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 one short, front-loaded sentence with no filler. It communicates the essential action and resource directly, and every word earns its place.

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?

For a simple status getter with fully documented parameters, the description is minimally adequate. However, the lack of an output schema means the description could have usefully stated the expected status values or the shape of the response. Without annotations, this leaves some ambiguity about what the agent should do with the result.

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%, so the schema already documents zone, vmName, and projectId effectively. The description adds no additional parameter meaning beyond what the schema provides, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb, 'Retrieve', and a clear resource, 'status of a Compute Engine VM instance'. It is distinct from sibling tools like start/stop/delete/list or IP retrieval, though it does not explicitly name a differentiating sibling.

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?

The usage context is implied: use this tool when you need the status of a single VM instance. However, it provides no explicit guidance about when not to use it, such as preferring list-instances when enumerating many VMs or when the instance details are already present.

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

Deploy Server