Google Compute Engine

get_disk_performance_config

Read-onlyIdempotent

Get performance configuration of a Compute Engine disk, including its type, size, provisioned IOPS, provisioned throughput, physical block size, storage pool and access mode. Requires project, zone, and disk name as input.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description
`type`	No	URL of the disk type resource.
`sizeGb`	No	Size of the disk in GB.
`accessMode`	No	The access mode of the disk.
`storagePool`	No	The storage pool of the disk.
`provisionedIops`	No	Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle.
`provisionedThroughput`	No	Indicates how much throughput to provision for the disk. This sets the number of throughput mb per second that the disk can handle.
`physicalBlockSizeBytes`	No	Physical block size of the persistent disk, in bytes.

TDQS

A4.3/5.0

Behavior4/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 adds value by specifying exactly what aspects of performance configuration will be returned, giving the agent a clear expectation of the tool's output scope.

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 two compact sentences with no filler. The primary purpose and output fields are front-loaded, followed by the required input summary, making it easy to scan and act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a rich output schema, complete parameter schema coverage, and annotations establishing read-only/idempotent behavior, the description covers everything needed to invoke the tool correctly. The listed fields and required inputs make the call unambiguous.

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 each parameter is already documented. The description restates that project, zone, and disk name are required but does not add deeper meaning about formats, defaults, or constraints beyond the schema.

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 uses a specific verb ('Get') and names a precise resource: the performance configuration of a Compute Engine disk. It enumerates the included fields (type, size, IOPS, throughput, block size, storage pool, access mode), which clearly distinguishes it from broader sibling tools like get_disk_basic_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly states the necessary inputs—project, zone, and disk name—so an agent knows what must be supplied. It does not explicitly compare itself to sibling getters or state when not to use it, but the configuration-specific scope provides adequate context for selection.

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?