Google Compute Engine

get_zone_operation

Read-onlyIdempotent

Get details of a zone operation, including its id, name, status, creation timestamp, error, warning, HTTP error message and HTTP error status code. Requires project, zone, and operation name as input.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Required. Identifier. The operation name.
`zone`	Yes	Required. The zone of the operation.
`project`	Yes	Required. Project ID for this request.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	The unique identifier for the operation.
`name`	No	Name of the operation.
`error`	No	Errors encountered during the operation execution.
`status`	No	The status of the operation.
`warnings`	No	Warnings encountered during the operation execution.
`createTime`	No	Creation timestamp of the operation.
`httpErrorMessage`	No	If the operation fails, this field contains the HTTP error message that corresponds to the HTTP error code generated for the audit log.
`httpErrorStatusCode`	No	If the operation fails, this field contains the HTTP error status code that corresponds to the HTTP error message generated for the audit log.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 26, 2026

changed

Output schema / properties / error / properties / errors / items / properties / errorDetails / items / properties / errorInfo / description

Previous value: -"Error information containing structured domain, reason, and metadata."New value: +"Error information containing structured domain, reason, and metadata. Only one of the following fields should be set: this field, quotaInfo, help, localizedMessage."

changed

Output schema / properties / error / properties / errors / items / properties / errorDetails / items / properties / help / description

Previous value: -"Links and information to help the user resolve the error."New value: +"Links and information to help the user resolve the error. Only one of the following fields should be set: this field, errorInfo, quotaInfo, localizedMessage."

changed

Output schema / properties / error / properties / errors / items / properties / errorDetails / items / properties / localizedMessage / description

Previous value: -"A localized human-readable error message intended for end users."New value: +"A localized human-readable error message intended for end users. Only one of the following fields should be set: this field, errorInfo, quotaInfo, help."

changed

Output schema / properties / error / properties / errors / items / properties / errorDetails / items / properties / quotaInfo / description

Previous value: -"Details about quota limits and metrics when a quota is exceeded."New value: +"Details about quota limits and metrics when a quota is exceeded. Only one of the following fields should be set: this field, errorInfo, help, localizedMessage."

Changed1 schema field changedAug 5, 2026

changedOutput schema / properties / warnings / items / properties / data / description

Previous value: -"[Output Only] Metadata about this warning in key: value format. For example: \"data\": [ { \"key\": \"scope\", \"value\": \"zones/us-east1-d\" } "New value: +"[Output Only] Metadata about this warning in key: value format. For example: \"data\": [ { \"key\": \"scope\", \"value\": \"zones/us-east1-d\" }] "

Changed7 schema fields changedJul 15, 2026
- addedOutput schema / properties / error / properties / errors / items / description
```
Added value: +"Represents a single error encountered during the processing of an operation."
```
- addedOutput schema / properties / error / properties / errors / items / properties / errorDetails / items / description
```
Added value: +"Container for structured error details providing additional context specific to the encountered error code."
```
- addedOutput schema / properties / error / properties / errors / items / properties / errorDetails / items / properties / errorInfo / description
```
Added value: +"Error information containing structured domain, reason, and metadata."
```
- addedOutput schema / properties / error / properties / errors / items / properties / errorDetails / items / properties / help / description
```
Added value: +"Links and information to help the user resolve the error."
```
- addedOutput schema / properties / error / properties / errors / items / properties / errorDetails / items / properties / localizedMessage / description
```
Added value: +"A localized human-readable error message intended for end users."
```
- addedOutput schema / properties / error / properties / errors / items / properties / errorDetails / items / properties / quotaInfo / description
```
Added value: +"Details about quota limits and metrics when a quota is exceeded."
```
- changedOutput schema / properties / status / x-google-enum-descriptions
```
Previous value: -[
-  "",
-  "",
-  ""
-]New value: +[
+  "The operation has completed processing successfully or with an error.",
+  "The operation is waiting to be processed.",
+  "The operation is actively being processed."
+]
```
First observedFeb 23, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'Get details' is consistent with those. The description adds the set of output fields but no additional behavioral traits such as error handling or auth requirements. Given annotation coverage, no contradiction and no further critical disclosure is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, first states action and key output fields, second states required inputs. No filler and easy to scan. Slight redundancy with the schema's required field list is acceptable for quick comprehension.

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?

For a simple read-only get operation with a rich output schema, the description covers the core inputs and result content. It doesn't describe temporal or error behavior, but those aren't needed for a straightforward getter. Complete enough for tool selection and invocation.

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 all three parameters are documented structurally. The description's 'Requires project, zone, and operation name as input' simply restates what the schema already declares, adding no new parameter semantics. Baseline 3 is appropriate because the schema carries the parameter documentation burden.

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 opens with 'Get details of a zone operation' – a specific verb and resource – and enumerates the returned fields. This clearly distinguishes it from create/list/mutate siblings and from getters for other resource types. It is precise enough for an agent to select it without opening the schema.

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 description makes the intended use clear: retrieving details of a zonal operation using project, zone, and operation name. It doesn't name alternatives or state when not to use it, but given the unique resource type and read-only semantics, this is adequate. No misleading guidance is present.

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

All Google Compute Engine tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?