Skip to main content
Glama

get_reservation_details

Read-onlyIdempotent

Get Compute Engine reservation details. Returns reservation details including name, ID, status, creation timestamp, specific reservation properties like machine type, guest accelerators and local SSDs, aggregate reservation properties like VM family and reserved resources, commitment and linked commitments, sharing settings, and resource status. Requires project, zone, and reservation name as input.

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Identifier. Name of the reservation to retrieve.
zoneYesRequired. The zone of the reservation.
projectYesRequired. Project ID for this request.

Output Schema

NameRequiredDescriptionDefault
idNoOutput only. [Output Only] The unique identifier for the resource. This identifier is defined by the server.
kindNoOutput only. [Output Only] Type of the resource. Always compute#reservations for reservations.compute#reservation
nameNoThe name of the resource, provided by the client when initially creating the resource. The resource name must be 1-63 characters long, and comply with RFC1035 <https://www.ietf.org/rfc/rfc1035.txt>. Specifically, the name must be 1-63 characters long and match the regular expression `[a-z]([-a-z0-9]*[a-z0-9])?` which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.
zoneNoZone in which the reservation resides. A zone must be provided if the reservation is created within a commitment.
paramsNoInput only. Additional params passed with the request, but not persisted as part of resource payload.
statusNoOutput only. [Output Only] The status of the reservation. - CREATING: Reservation resources are being allocated. - READY: Reservation resources have been allocated, and the reservation is ready for use. - DELETING: Reservation deletion is in progress. - UPDATING: Reservation update is in progress.
selfLinkNoOutput only. [Output Only] Server-defined fully-qualified URL for this resource.
commitmentNoOutput only. [Output Only] Full or partial URL to a parent commitment. This field displays for reservations that are tied to a commitment.
descriptionNoAn optional description of this resource. Provide this property when you create the resource.
deleteAtTimeNoAbsolute time in future when the reservation will be auto-deleted by Compute Engine. Timestamp is represented in RFC3339 <https://www.ietf.org/rfc/rfc3339.txt> text format. Only one of this field or deleteAfterDuration should be set.
satisfiesPzsNoOutput only. [Output Only] Reserved for future use.
shareSettingsNoSpecify share-settings to create a shared reservation. This property is optional. For more information about the syntax and options for this field and its subfields, see the guide for creating a shared reservation. <https://cloud.google.com/compute/docs/instances/reservations-shared#creating_a_shared_reservation>
deploymentTypeNoSpecifies the deployment strategy for this reservation.
protectionTierNoProtection tier for the workload which specifies the workload expectations in the event of infrastructure failures at data center (e.g. power and/or cooling failures).
resourceStatusNoOutput only. [Output Only] Status information for Reservation resource.
schedulingTypeNoThe type of maintenance for the reservation.
resourceMetadataNoOutput only. [Output Only] Contains standard resource metadata for an Allocation resource. It is populated for each instance of the Allocation resource, and includes the api_version the instance was retrieved through, and its canonical resource_type name.
resourcePoliciesNoResource policies to be added to this reservation. The key is defined by user, and the value is resource policy url. This is to define placement policy with reservation.
creationTimestampNoOutput only. [Output Only] Creation timestamp in RFC3339 <https://www.ietf.org/rfc/rfc3339.txt> text format.
linkedCommitmentsNoOutput only. [Output Only] Full or partial URL to parent commitments. This field displays for reservations that are tied to multiple commitments.
deleteAfterDurationNoDuration time relative to reservation creation when Compute Engine will automatically delete this resource. Only one of this field or deleteAtTime should be set.
specificReservationNoReservation for instances with specific machine shapes. Only one of this field or aggregateReservation should be set.
aggregateReservationNoReservation for aggregated resources, providing shape flexibility. Only one of this field or specificReservation should be set.
earlyAccessMaintenanceNoIndicates the early access maintenance for the reservation. If this field is absent or set to NO_EARLY_ACCESS, the reservation is not enrolled in early access maintenance and the standard notice applies.
confidentialComputeTypeNo
reservationSharingPolicyNoSpecify the reservation sharing policy. If unspecified, the reservation will not be shared with Google Cloud managed services.
advancedDeploymentControlNoAdvanced control for cluster management, applicable only to DENSE deployment type reservations.
enableEmergentMaintenanceNoIndicates whether Compute Engine allows unplanned maintenance for your VMs; for example, to fix hardware errors.
specificReservationRequiredNoIndicates whether the reservation can be consumed by VMs with affinity for "any" reservation. If the field is set, then only VMs that target the reservation by name can consume from this reservation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / $defs / UpcomingMaintenance / properties / maintenanceReasons / items / enum
      Previous value: -[
      -  "FAILURE_DISK",
      -  "FAILURE_GPU",
      -  "FAILURE_GPU_MULTIPLE_FAULTY_HOSTS_CUSTOMER_REPORTED",
      -  "FAILURE_GPU_NVLINK_SWITCH_CUSTOMER_REPORTED",
      -  "FAILURE_GPU_TEMPERATURE",
      -  "FAILURE_GPU_XID",
      -  "FAILURE_INFRA",
      -  "FAILURE_INTERFACE",
      -  "FAILURE_MEMORY",
      -  "FAILURE_NETWORK",
      -  "FAILURE_NVLINK",
      -  "FAILURE_REDUNDANT_HARDWARE_FAULT",
      -  "FAILURE_TPU",
      -  "INFRASTRUCTURE_RELOCATION",
      -  "MAINTENANCE_REASON_UNKNOWN",
      -  "PLANNED_NETWORK_UPDATE",
      -  "PLANNED_UPDATE"
      -]New value: +[
      +  "FAILURE_CUSTOMER_REPORTED",
      +  "FAILURE_DISK",
      +  "FAILURE_GPU",
      +  "FAILURE_GPU_MULTIPLE_FAULTY_HOSTS_CUSTOMER_REPORTED",
      +  "FAILURE_GPU_NVLINK_SWITCH_CUSTOMER_REPORTED",
      +  "FAILURE_GPU_TEMPERATURE",
      +  "FAILURE_GPU_XID",
      +  "FAILURE_INFRA",
      +  "FAILURE_INTERFACE",
      +  "FAILURE_MEMORY",
      +  "FAILURE_NETWORK",
      +  "FAILURE_NVLINK",
      +  "FAILURE_REDUNDANT_HARDWARE_FAULT",
      +  "FAILURE_TPU",
      +  "INFRASTRUCTURE_RELOCATION",
      +  "MAINTENANCE_REASON_UNKNOWN",
      +  "PLANNED_NETWORK_UPDATE",
      +  "PLANNED_UPDATE"
      +]
    • changedOutput schema / $defs / UpcomingMaintenance / properties / maintenanceReasons / items / x-google-enum-descriptions
      Previous value: -[
      -  "Maintenance due to disk errors.",
      -  "Maintenance due to GPU errors.",
      -  "Maintenance due to customer reported multiple faulty hosts via R&R Subblock API.",
      -  "Maintenance due to customer reported NVLink switch failure via R&R Subblock API.",
      -  "Maintenance due to high GPU temperature.",
      -  "Maintenance due to GPU xid failure.",
      -  "Maintenance due to infrastructure errors.",
      -  "Maintenance due to interface errors.",
      -  "Maintenance due to memory errors.",
      -  "Maintenance due to network errors.",
      -  "Maintenance due to NVLink failure.",
      -  "Maintenance due to redundant hardware fault.",
      -  "Maintenance due to TPU errors.",
      -  "Maintenance due to infrastructure relocation.",
      -  "Unknown maintenance reason. Do not use this value.",
      -  "Maintenance due to planned network update.",
      -  "Maintenance due to planned update to the instance."
      -]New value: +[
      +  "Maintenance due to a fault reported by the customer via the R&R (Report-and-Replace) API.",
      +  "Maintenance due to disk errors.",
      +  "Maintenance due to GPU errors.",
      +  "Maintenance due to customer reported multiple faulty hosts via R&R Subblock API.",
      +  "Maintenance due to customer reported NVLink switch failure via R&R Subblock API.",
      +  "Maintenance due to high GPU temperature.",
      +  "Maintenance due to GPU xid failure.",
      +  "Maintenance due to infrastructure errors.",
      +  "Maintenance due to interface errors.",
      +  "Maintenance due to memory errors.",
      +  "Maintenance due to network errors.",
      +  "Maintenance due to NVLink failure.",
      +  "Maintenance due to redundant hardware fault.",
      +  "Maintenance due to TPU errors.",
      +  "Maintenance due to infrastructure relocation.",
      +  "Unknown maintenance reason. Do not use this value.",
      +  "Maintenance due to planned network update.",
      +  "Maintenance due to planned update to the instance."
      +]
  2. Changed5 schema fields changed
    • addedOutput schema / $defs / ResourceStatus / properties / machineCount
      Added value: +{
      +  "description": "The number of machines in the reservation. Only populated for families where machine to host ratio is not 1:1 such as TPU8i.",
      +  "format": "int32",
      +  "type": "integer"
      +}
    • changedOutput schema / properties / aggregateReservation / description
      Previous value: -"Reservation for aggregated resources, providing shape flexibility."New value: +"Reservation for aggregated resources, providing shape flexibility. Only one of this field or specificReservation should be set."
    • changedOutput schema / properties / deleteAfterDuration / description
      Previous value: -"Duration time relative to reservation creation when Compute Engine will automatically delete this resource."New value: +"Duration time relative to reservation creation when Compute Engine will automatically delete this resource. Only one of this field or deleteAtTime should be set."
    • changedOutput schema / properties / deleteAtTime / description
      Previous value: -"Absolute time in future when the reservation will be auto-deleted by Compute Engine. Timestamp is represented in RFC3339 <https://www.ietf.org/rfc/rfc3339.txt> text format."New value: +"Absolute time in future when the reservation will be auto-deleted by Compute Engine. Timestamp is represented in RFC3339 <https://www.ietf.org/rfc/rfc3339.txt> text format. Only one of this field or deleteAfterDuration should be set."
    • changedOutput schema / properties / specificReservation / description
      Previous value: -"Reservation for instances with specific machine shapes."New value: +"Reservation for instances with specific machine shapes. Only one of this field or aggregateReservation should be set."
  3. Changed2 schema fields changed
    • changedOutput schema / properties / confidentialComputeType / enum
      Previous value: -[
      -  "CONFIDENTIAL_COMPUTE_TYPE_TDX",
      -  "CONFIDENTIAL_COMPUTE_TYPE_UNSPECIFIED"
      -]New value: +[
      +  "CONFIDENTIAL_COMPUTE_TYPE_BMSAI",
      +  "CONFIDENTIAL_COMPUTE_TYPE_TDX",
      +  "CONFIDENTIAL_COMPUTE_TYPE_UNSPECIFIED"
      +]
    • changedOutput schema / properties / confidentialComputeType / x-google-enum-descriptions
      Previous value: -[
      -  "Intel Trust Domain Extensions.",
      -  ""
      -]New value: +[
      +  "Bare Metal Secure AI.",
      +  "Intel Trust Domain Extensions.",
      +  ""
      +]
  4. Changed3 schema fields changed
    • addedOutput schema / $defs / ResourceMetadata
      Added value: +{
      +  "description": "Standardized resource metadata common to all compute resources.",
      +  "properties": {
      +    "apiVersion": {
      +      "description": "The version of the API interface that this resource was retrieved through. For example, `\"2025-01-01\"` or `\"2025-01-01-preview\"`.",
      +      "type": "string"
      +    },
      +    "resourceType": {
      +      "description": "The canonical resource type name in the format of a resource type as defined by [AIP-123](https://google.aip.dev/123). For example, `\"compute.googleapis.com/Instance\"`.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / confidentialComputeType
      Added value: +{
      +  "enum": [
      +    "CONFIDENTIAL_COMPUTE_TYPE_TDX",
      +    "CONFIDENTIAL_COMPUTE_TYPE_UNSPECIFIED"
      +  ],
      +  "type": "string",
      +  "x-google-enum-descriptions": [
      +    "Intel Trust Domain Extensions.",
      +    ""
      +  ]
      +}
    • addedOutput schema / properties / resourceMetadata
      Added value: +{
      +  "$ref": "#/$defs/ResourceMetadata",
      +  "description": "Output only. [Output Only] Contains standard resource metadata for an Allocation resource. It is populated for each instance of the Allocation resource, and includes the api_version the instance was retrieved through, and its canonical resource_type name.",
      +  "readOnly": true
      +}
  5. Changed1 schema field changed
    • removedOutput schema / properties / confidentialComputeType
      Removed value: -{
      -  "enum": [
      -    "CONFIDENTIAL_COMPUTE_TYPE_TDX",
      -    "CONFIDENTIAL_COMPUTE_TYPE_UNSPECIFIED"
      -  ],
      -  "type": "string",
      -  "x-google-enum-descriptions": [
      -    "Intel Trust Domain Extensions.",
      -    ""
      -  ]
      -}
  6. Changed1 schema field changed
    • addedOutput schema / properties / confidentialComputeType
      Added value: +{
      +  "enum": [
      +    "CONFIDENTIAL_COMPUTE_TYPE_TDX",
      +    "CONFIDENTIAL_COMPUTE_TYPE_UNSPECIFIED"
      +  ],
      +  "type": "string",
      +  "x-google-enum-descriptions": [
      +    "Intel Trust Domain Extensions.",
      +    ""
      +  ]
      +}
  7. Changed1 schema field changed
    • removedOutput schema / properties / confidentialComputeType
      Removed value: -{
      -  "enum": [
      -    "CONFIDENTIAL_COMPUTE_TYPE_TDX",
      -    "CONFIDENTIAL_COMPUTE_TYPE_UNSPECIFIED"
      -  ],
      -  "type": "string",
      -  "x-google-enum-descriptions": [
      -    "Intel Trust Domain Extensions.",
      -    ""
      -  ]
      -}
  8. Changed1 schema field changed
    • addedOutput schema / properties / confidentialComputeType
      Added value: +{
      +  "enum": [
      +    "CONFIDENTIAL_COMPUTE_TYPE_TDX",
      +    "CONFIDENTIAL_COMPUTE_TYPE_UNSPECIFIED"
      +  ],
      +  "type": "string",
      +  "x-google-enum-descriptions": [
      +    "Intel Trust Domain Extensions.",
      +    ""
      +  ]
      +}
  9. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description usefully signals the breadth of returned data (commitments, sharing settings, resource status), which helps the agent judge whether this heavier call is warranted, but adds nothing on errors, permissions, or latency.

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?

Purpose is front-loaded and the single paragraph is dominated by substantive return-field detail. The trailing sentence restating the required inputs is redundant with the schema and slightly pads the definition.

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?

With an output schema present, the description needn't explain return values, and inputs are 100% covered, so the core is adequate. The notable omission is any signal about how this differs from 'get_reservation_basic_info', which the agent needs to choose correctly between two similar reads.

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 ('project', 'zone', 'name') are fully documented in the schema. The description's 'Requires project, zone, and reservation name as input' merely restates them with no added format or constraint detail, so the baseline 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 opens with a specific verb+resource ('Get Compute Engine reservation details') and enumerates the returned fields, so the tool's function is unmistakable. However, it does not distinguish itself from the close sibling 'get_reservation_basic_info', leaving the agent to guess which one to pick.

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?

There is no explicit when-to-use guidance and no alternatives named, despite a same-resource sibling ('get_reservation_basic_info') that clearly overlaps. The only conditional content is a restatement that project, zone, and name are required, which is not usage guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources