Skip to main content
Glama

Google Compute Engine

by com.googleapis.compute
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
nameYesRequired. Identifier. The instance name.
zoneYesRequired. The zone of the instance.
projectYesRequired. Project ID for this request.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
attachedDisksNoThe list of attached disks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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",
-  "SUSPEND_SAFE_FPR",
-  "TDX_CAPABLE",
-  "UEFI_COMPATIBLE",
-  "VIRTIO_SCSI_MULTIQUEUE",
-  "WINDOWS"
-]New value: +[
+  "BARE_METAL_LINUX_COMPATIBLE",
+  "BMSAI_CAPABLE",
+  "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: -[
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "",
-  "Indicates the guest OS is safe for free page reporting (FPR) during suspend.",
-  "",
-  "",
-  "",
-  ""
-]New value: +[
+  "",
+  "Indicates the guest OS is capable of Bare Metal Secure AI (BMSAI) confidential computing.",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "",
+  "Indicates the guest OS is safe for free page reporting (FPR) during suspend.",
+  "",
+  "",
+  "",
+  ""
+]
  2. Changed3 schema fields changed
    • 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.",
+  "",
+  "",
+  "",
+  ""
+]
  3. Changed7 schema fields changed
    • 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>."
  4. Changed3 schema fields changed
    • 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."
  5. Changed1 schema field changed
    • 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."
  6. Changed1 schema field changed
    • 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> ."
  7. Changed1 schema field changed
    • 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> ."
  8. Changed1 schema field changed
    • 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> ."
  9. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already convey read-only, idempotent, and non-destructive behavior, so the bar for additional behavioral disclosure is lower. The description adds useful context by enumerating the response fields (kind, type, mode, boot, encryption key, etc.) but does not reveal other behavioral traits like pagination, permissions, or error conditions. No contradiction with annotations.

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?

The main purpose is front-loaded in a single sentence, followed by a specific list of response fields. The list is long and includes a minor typo ('licenses,, interface'), but the structure is otherwise clear and efficient. Every part contributes useful information.

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 list operation, this description is reasonably complete: it names the resource, lists the required inputs, and describes the response contents. An output schema exists and annotations are rich, so the description does not need to explain return values or safety. It lacks explicit sibling routing, but that is already captured in usage guidelines.

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 coverage is 100% and each parameter already has a descriptive explanation ('Project ID for this request', 'The zone of the instance', 'The instance name'). The description only repeats that project, zone, and instance name are required, adding no semantic information beyond what the schema already provides.

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 'Lists' and a specific resource 'disks attached to a Compute Engine VM instance', which makes the tool's function unmistakable. It is also clearly distinct from sibling tools like list_disks (project-level) and list_instances (VM-level), so an agent can differentiate it without needing to open schemas.

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 implies when to use the tool—when you need attached disks for a specific instance—but it never explicitly states that, nor does it compare with alternatives such as list_disks. There is no mention of exclusions or conditions that would route the agent to a sibling tool.

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 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources