Google Compute Engine

list_instance_attached_disks

Read-onlyIdempotent

Lists the disks attached to a Compute Engine virtual machine (VM) instance. For each attached disk, the response includes details such as kind, type, mode, saved state, source, device name, index, boot, initialize parameters, auto delete, licenses,, interface, guest OS features, disk encryption key, disk size, shielded instance initial state, force attach, and architecture. Requires project, zone, and instance name as input.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`attachedDisks`	No	The list of attached disks.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedAug 25, 2026

changedOutput schema / $defs / GuestOsFeature / properties / type / description

Previous value: -"The ID of a supported feature. To add multiple values, use commas to separate values. Set to one or more of the following values: - VIRTIO_SCSI_MULTIQUEUE - WINDOWS - MULTI_IP_SUBNET - UEFI_COMPATIBLE - GVNIC - SEV_CAPABLE - SUSPEND_RESUME_COMPATIBLE - SEV_LIVE_MIGRATABLE_V2 - SEV_SNP_CAPABLE - TDX_CAPABLE - IDPF - SNP_SVSM_CAPABLE - CCA_CAPABLE For more information, see Enabling guest operating system features </compute/docs/images/create-delete-deprecate-private-images#guest-os-features> ."New value: +"The ID of a supported feature. To add multiple values, use commas to separate values. Set to one or more of the following values: - VIRTIO_SCSI_MULTIQUEUE - WINDOWS - MULTI_IP_SUBNET - UEFI_COMPATIBLE - GVNIC - SEV_CAPABLE - SUSPEND_RESUME_COMPATIBLE - SEV_LIVE_MIGRATABLE_V2 - SEV_SNP_CAPABLE - TDX_CAPABLE - IDPF - SNP_SVSM_CAPABLE - CCA_CAPABLE - SUSPEND_SAFE_FPR For more information, see Enabling guest operating system features </compute/docs/images/create-delete-deprecate-private-images#guest-os-features> ."

changedOutput schema / $defs / GuestOsFeature / properties / type / enum

Previous value: -[
-  "BARE_METAL_LINUX_COMPATIBLE",
-  "CCA_CAPABLE",
-  "FEATURE_TYPE_UNSPECIFIED",
-  "GVNIC",
-  "IDPF",
-  "MULTI_IP_SUBNET",
-  "SECURE_BOOT",
-  "SEV_CAPABLE",
-  "SEV_LIVE_MIGRATABLE",
-  "SEV_LIVE_MIGRATABLE_V2",
-  "SEV_SNP_CAPABLE",
-  "SNP_SVSM_CAPABLE",
-  "TDX_CAPABLE",
-  "UEFI_COMPATIBLE",
-  "VIRTIO_SCSI_MULTIQUEUE",
-  "WINDOWS"
-]New value: +[
+  "BARE_METAL_LINUX_COMPATIBLE",
+  "CCA_CAPABLE",
+  "FEATURE_TYPE_UNSPECIFIED",
+  "GVNIC",
+  "IDPF",
+  "MULTI_IP_SUBNET",
+  "SECURE_BOOT",
+  "SEV_CAPABLE",
+  "SEV_LIVE_MIGRATABLE",
+  "SEV_LIVE_MIGRATABLE_V2",
+  "SEV_SNP_CAPABLE",
+  "SNP_SVSM_CAPABLE",
+  "SUSPEND_SAFE_FPR",
+  "TDX_CAPABLE",
+  "UEFI_COMPATIBLE",
+  "VIRTIO_SCSI_MULTIQUEUE",
+  "WINDOWS"
+]

changedOutput schema / $defs / GuestOsFeature / properties / type / x-google-enum-descriptions

Previous value: -[
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  ""
-]New value: +[
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "Indicates the guest OS is safe for free page reporting (FPR) during suspend.",
+  "",
+  "",
+  "",
+  ""
+]

Changed7 schema fields changedJul 26, 2026

addedOutput schema / $defs / CustomerEncryptionKey / properties / rawKey / deprecated
```
Added value: +true
```

changedOutput schema / $defs / CustomerEncryptionKey / properties / rawKey / description

Previous value: -"Specifies a 256-bit customer-supplied encryption key </compute/docs/disks/customer-supplied-encryption>, encoded in RFC 4648 base64 <https://tools.ietf.org/html/rfc4648#section-4> to either encrypt or decrypt this resource. You can provide either the rawKey or the rsaEncryptedKey. For example: \"rawKey\": \"SGVsbG8gZnJvbSBHb29nbGUgQ2xvdWQgUGxhdGZvcm0=\" "New value: +"[DEPRECATED] CSEK is no longer supported. Use CMEK instead. Specifies a 256-bit customer-supplied encryption key </compute/docs/disks/customer-supplied-encryption>, encoded in RFC 4648 base64 <https://tools.ietf.org/html/rfc4648#section-4> to either encrypt or decrypt this resource. You can provide either the rawKey or the rsaEncryptedKey. For example: \"rawKey\": \"SGVsbG8gZnJvbSBHb29nbGUgQ2xvdWQgUGxhdGZvcm0=\" "

addedOutput schema / $defs / CustomerEncryptionKey / properties / rsaEncryptedKey / deprecated
```
Added value: +true
```

changedOutput schema / $defs / CustomerEncryptionKey / properties / rsaEncryptedKey / description

Previous value: -"Specifies an RFC 4648 base64 encoded, RSA-wrapped 2048-bit customer-supplied encryption key </compute/docs/disks/customer-supplied-encryption#rsa-encryption> to either encrypt or decrypt this resource. You can provide either the rawKey or the rsaEncryptedKey. For example: \"rsaEncryptedKey\": \"ieCx/NcW06PcT7Ep1X6LUTc/hLvUDYyzSZPPVCVPTVEohpeHASqC8uw5TzyO9U+Fka9JFH z0mBibXUInrC/jEk014kCK/NPjYgEMOyssZ4ZINPKxlUh2zn1bV+MCaTICrdmuSBTWlUUiFoD D6PYznLwh8ZNdaheCeZ8ewEXgFQ8V+sDroLaN3Xs3MDTXQEMMoNUXMCZEIpg9Vtp9x2oe==\" The key must meet the following requirements before you can provide it to Compute Engine: 1. The key is wrapped using a RSA public key certificate provided by Google. 2. After being wrapped, the key must be encoded in RFC 4648 base64 <https://tools.ietf.org/html/rfc4648#section-4> encoding. Gets the RSA public key certificate provided by Google at: https://cloud-certs.storage.googleapis.com/google-cloud-csek-ingress.pem "New value: +"[DEPRECATED] CSEK is no longer supported. Use CMEK instead. Specifies an RFC 4648 base64 encoded, RSA-wrapped 2048-bit customer-supplied encryption key </compute/docs/disks/customer-supplied-encryption#rsa-encryption> to either encrypt or decrypt this resource. You can provide either the rawKey or the rsaEncryptedKey. For example: \"rsaEncryptedKey\": \"ieCx/NcW06PcT7Ep1X6LUTc/hLvUDYyzSZPPVCVPTVEohpeHASqC8uw5TzyO9U+Fka9JFH z0mBibXUInrC/jEk014kCK/NPjYgEMOyssZ4ZINPKxlUh2zn1bV+MCaTICrdmuSBTWlUUiFoD D6PYznLwh8ZNdaheCeZ8ewEXgFQ8V+sDroLaN3Xs3MDTXQEMMoNUXMCZEIpg9Vtp9x2oe==\" The key must meet the following requirements before you can provide it to Compute Engine: 1. The key is wrapped using a RSA public key certificate provided by Google. 2. After being wrapped, the key must be encoded in RFC 4648 base64 <https://tools.ietf.org/html/rfc4648#section-4> encoding. Gets the RSA public key certificate provided by Google at: https://cloud-certs.storage.googleapis.com/google-cloud-csek-ingress.pem "

addedOutput schema / $defs / CustomerEncryptionKey / properties / sha256 / deprecated
```
Added value: +true
```

changedOutput schema / $defs / CustomerEncryptionKey / properties / sha256 / description

Previous value: -"[Output only] The RFC 4648 base64 <https://tools.ietf.org/html/rfc4648#section-4> encoded SHA-256 hash of the customer-supplied encryption key </compute/docs/disks/customer-supplied-encryption> that protects this resource."New value: +"[DEPRECATED] CSEK is no longer supported. Use CMEK instead. [Output only] The RFC 4648 base64 <https://tools.ietf.org/html/rfc4648#section-4> encoded SHA-256 hash of the customer-supplied encryption key </compute/docs/disks/customer-supplied-encryption> that protects this resource."

addedOutput schema / $defs / InitializeParams / properties / diskType / description

Added value: +"Specifies the disk type used for the boot disk or an additional data disk. For valid disk type values, see Supported types for Hyperdisk volumes </compute/docs/disks/add-hyperdisk#hd_disk_types> and Persistent Disk type variables </compute/docs/disks/add-persistent-disk#hd_disk_types>. When creating a single instance, you must provide either the full or partial URL of the disk type. For example, the following values are valid: - https://www.googleapis.com/compute/v1/projects/project/zones/zone /diskTypes/diskType - projects/project/zones/zone/diskTypes/diskType - zones/zone/diskTypes/diskType When creating an instance template, instance flexibility policy, or when creating or updating an all-instances configuration, you specify the disk type without a URL, for example, hyperdisk-balanced. If you omit this field for a disk, the default disk type depends on the instance's machine series, as follows. - For first- and second-generation machine series like N1, N2, T2, and M1, the default disk type is Standard Persistent Disk (pd-standard). - For C3, C3D, and M3 the default is Balanced Persistent Disk ( pd-balanced). - For other third-generation machine series like A3, H3, Z3, all fourth-generation types like C4, N4, M4, and newer machine series, the default is Hyperdisk Balanced (hyperdisk-balanced). The disk type you specify must be compatible with the instance's machine series. For a list of machine series that support Persistent Disk, see Machine series support for Persistent Disk </compute/docs/disks/persistent-disks#pd-machine-series>. For a list of machine series that support Hyperdisk, see Machine series support for Hyperdisk </compute/docs/disks/hyperdisks#machine-type-support>."

Changed3 schema fields changedMay 16, 2026

changedOutput schema / $defs / GuestOsFeature / properties / type / enum

Previous value: -[
-  "BARE_METAL_LINUX_COMPATIBLE",
-  "FEATURE_TYPE_UNSPECIFIED",
-  "GVNIC",
-  "IDPF",
-  "MULTI_IP_SUBNET",
-  "SECURE_BOOT",
-  "SEV_CAPABLE",
-  "SEV_LIVE_MIGRATABLE",
-  "SEV_LIVE_MIGRATABLE_V2",
-  "SEV_SNP_CAPABLE",
-  "SNP_SVSM_CAPABLE",
-  "TDX_CAPABLE",
-  "UEFI_COMPATIBLE",
-  "VIRTIO_SCSI_MULTIQUEUE",
-  "WINDOWS"
-]New value: +[
+  "BARE_METAL_LINUX_COMPATIBLE",
+  "CCA_CAPABLE",
+  "FEATURE_TYPE_UNSPECIFIED",
+  "GVNIC",
+  "IDPF",
+  "MULTI_IP_SUBNET",
+  "SECURE_BOOT",
+  "SEV_CAPABLE",
+  "SEV_LIVE_MIGRATABLE",
+  "SEV_LIVE_MIGRATABLE_V2",
+  "SEV_SNP_CAPABLE",
+  "SNP_SVSM_CAPABLE",
+  "TDX_CAPABLE",
+  "UEFI_COMPATIBLE",
+  "VIRTIO_SCSI_MULTIQUEUE",
+  "WINDOWS"
+]

changedOutput schema / $defs / GuestOsFeature / properties / type / x-google-enum-descriptions

Previous value: -[
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  ""
-]New value: +[
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  ""
+]

removedOutput schema / $defs / InitializeParams / properties / diskType / description

Removed value: -"Specifies the disk type to use to create the instance. If not specified, the default is pd-standard, specified using the full URL. For example: https://www.googleapis.com/compute/v1/projects/project/zones/zone /diskTypes/pd-standard For a full list of acceptable values, see Persistent disk types </compute/docs/disks#disk-types>. If you specify this field when creating a VM, you can provide either the full or partial URL. For example, the following values are valid: - https://www.googleapis.com/compute/v1/projects/project/zones/zone /diskTypes/diskType - projects/project/zones/zone/diskTypes/diskType - zones/zone/diskTypes/diskType If you specify this field when creating or updating an instance template or all-instances configuration, specify the type of the disk, not the URL. For example: pd-standard."

Changed1 schema field changedApr 28, 2026

changedOutput schema / $defs / InitializeParams / properties / resourceManagerTags / description

Previous value: -"Input only. Resource manager tags to be bound to the disk. Tag keys and values have the same definition as resource manager tags <https://cloud.google.com/resource-manager/docs/tags/tags-overview>. Keys and values can be either in numeric format, such as `tagKeys/{tag_key_id}` and `tagValues/456` or in namespaced format such as `{org_id|project_id}/{tag_key_short_name}` and `{tag_value_short_name}`. The field is ignored (both PUT & PATCH) when empty."New value: +"Input only. Resource manager tags to be bound to the disk. Tag keys and values have the same definition as resource manager tags <https://cloud.google.com/resource-manager/docs/tags/tags-overview>. Keys and values can be either in numeric format, such as `tagKeys/{tag_key_id}` and `tagValues/{tag_value_id}` or in namespaced format such as `{org_id|project_id}/{tag_key_short_name}` and `{tag_value_short_name}`. The field is ignored (both PUT & PATCH) when empty."

Changed1 schema field changedApr 6, 2026

changedOutput schema / $defs / GuestOsFeature / properties / type / description

Previous value: -"The ID of a supported feature. To add multiple values, use commas to separate values. Set to one or more of the following values: - VIRTIO_SCSI_MULTIQUEUE - WINDOWS - MULTI_IP_SUBNET - UEFI_COMPATIBLE - GVNIC - SEV_CAPABLE - SUSPEND_RESUME_COMPATIBLE - SEV_LIVE_MIGRATABLE_V2 - SEV_SNP_CAPABLE - TDX_CAPABLE - IDPF - SNP_SVSM_CAPABLE For more information, see Enabling guest operating system features </compute/docs/images/create-delete-deprecate-private-images#guest-os-features> ."New value: +"The ID of a supported feature. To add multiple values, use commas to separate values. Set to one or more of the following values: - VIRTIO_SCSI_MULTIQUEUE - WINDOWS - MULTI_IP_SUBNET - UEFI_COMPATIBLE - GVNIC - SEV_CAPABLE - SUSPEND_RESUME_COMPATIBLE - SEV_LIVE_MIGRATABLE_V2 - SEV_SNP_CAPABLE - TDX_CAPABLE - IDPF - SNP_SVSM_CAPABLE - CCA_CAPABLE For more information, see Enabling guest operating system features </compute/docs/images/create-delete-deprecate-private-images#guest-os-features> ."

Changed1 schema field changedMar 30, 2026

changedOutput schema / $defs / GuestOsFeature / properties / type / description

Previous value: -"The ID of a supported feature. To add multiple values, use commas to separate values. Set to one or more of the following values: - VIRTIO_SCSI_MULTIQUEUE - WINDOWS - MULTI_IP_SUBNET - UEFI_COMPATIBLE - GVNIC - SEV_CAPABLE - SUSPEND_RESUME_COMPATIBLE - SEV_LIVE_MIGRATABLE_V2 - SEV_SNP_CAPABLE - TDX_CAPABLE - IDPF - SNP_SVSM_CAPABLE - CCA_CAPABLE For more information, see Enabling guest operating system features </compute/docs/images/create-delete-deprecate-private-images#guest-os-features> ."New value: +"The ID of a supported feature. To add multiple values, use commas to separate values. Set to one or more of the following values: - VIRTIO_SCSI_MULTIQUEUE - WINDOWS - MULTI_IP_SUBNET - UEFI_COMPATIBLE - GVNIC - SEV_CAPABLE - SUSPEND_RESUME_COMPATIBLE - SEV_LIVE_MIGRATABLE_V2 - SEV_SNP_CAPABLE - TDX_CAPABLE - IDPF - SNP_SVSM_CAPABLE For more information, see Enabling guest operating system features </compute/docs/images/create-delete-deprecate-private-images#guest-os-features> ."

Changed1 schema field changedMar 26, 2026

changedOutput schema / $defs / GuestOsFeature / properties / type / description

Previous value: -"The ID of a supported feature. To add multiple values, use commas to separate values. Set to one or more of the following values: - VIRTIO_SCSI_MULTIQUEUE - WINDOWS - MULTI_IP_SUBNET - UEFI_COMPATIBLE - GVNIC - SEV_CAPABLE - SUSPEND_RESUME_COMPATIBLE - SEV_LIVE_MIGRATABLE_V2 - SEV_SNP_CAPABLE - TDX_CAPABLE - IDPF - SNP_SVSM_CAPABLE For more information, see Enabling guest operating system features </compute/docs/images/create-delete-deprecate-private-images#guest-os-features> ."New value: +"The ID of a supported feature. To add multiple values, use commas to separate values. Set to one or more of the following values: - VIRTIO_SCSI_MULTIQUEUE - WINDOWS - MULTI_IP_SUBNET - UEFI_COMPATIBLE - GVNIC - SEV_CAPABLE - SUSPEND_RESUME_COMPATIBLE - SEV_LIVE_MIGRATABLE_V2 - SEV_SNP_CAPABLE - TDX_CAPABLE - IDPF - SNP_SVSM_CAPABLE - CCA_CAPABLE For more information, see Enabling guest operating system features </compute/docs/images/create-delete-deprecate-private-images#guest-os-features> ."

First observedFeb 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds detail about the response fields (e.g., kind, type, mode) which is useful context beyond the annotations. However, it does not disclose any additional behavioral traits such as pagination, rate limits, or authentication requirements. No contradiction exists. With annotations present, the description provides moderate added value.

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

Conciseness3/5

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

The description is informative but somewhat verbose. It front-loads the main purpose and then lists many response fields, which is useful. However, the closing sentence 'Requires project, zone, and instance name as input.' is redundant given the schema's required fields and could be trimmed. Overall, it is structured in a single sentence but includes a lengthy enumeration that could be more concise.

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 read-only list tool with an output schema available, the description is fairly complete. It clearly states the operation, the required inputs, and the nature of the response (listing attached disks with many fields). It does not mention pagination or filtering, but the presence of an output schema likely covers return structure. Given the tool's simplicity and annotation support, no critical information is missing.

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?

The input schema has 100% description coverage for all three required parameters (project, zone, name). The description only restates that these are required, without adding meaning beyond what the schema already provides. Since the schema fully documents each parameter, a baseline of 3 is appropriate.

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 clearly states the specific verb 'Lists' and the resource 'disks attached to a Compute Engine virtual machine (VM) instance'. It distinguishes itself from sibling tools like list_disks and list_instances by focusing on attached disks of a specific instance, making the purpose unambiguous.

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 does not provide explicit guidance on when to use this tool versus alternatives. It only states what it does and mentions required inputs. No exclusions or routing to sibling tools like list_disks or get_instance_basic_info are given, leaving the agent to infer the appropriate context.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation5/5

Each tool targets a distinct resource-action combination. For resources with both basic and detailed getters (reservations, templates), the suffixes clearly differentiate them, and list vs get distinctions are unambiguous. No two tools appear to do the same thing.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_instance, list_disks, get_zone_operation). Getters consistently use descriptive suffixes like basic_info, details, or properties. No mixed naming conventions or vague verbs.

Tool Count4/5

29 tools is slightly above the ideal range but justified given the breadth of Google Compute Engine resources covered (instances, disks, templates, reservations, commitments, MIGs, snapshots, images, machine types, accelerator types). Each tool serves a specific purpose and contributes to the overall scope.

Completeness2/5

The toolset is heavily read-oriented. While instances have full lifecycle coverage (create, delete, start, stop, reset, set machine type), most other resources lack write operations: disks, templates, reservations, commitments, snapshots, and MIGs only have get/list tools. This creates dead ends for agents needing to create or modify these resources, which is a significant gap for a GCE management server.

Resources

Need Help?