Tool: list_commitments
Lists Compute Engine Commitments in a region. Details for each commitment include name, ID, status, plan, type, resources, and creation, start and end timestamps. Requires project and region as input.
The following sample demonstrate how to use curl to invoke the list_commitments MCP tool.
| Curl Request |
|---|
curl --location 'https://compute.googleapis.com/mcp' \ --header 'content-type: application/json' \ --header 'accept: application/json, text/event-stream' \ --data '{ "method": "tools/call", "params": { "name": "list_commitments", "arguments": { // provide these details according to the tool's MCP specification } }, "jsonrpc": "2.0", "id": 1 }' |
Input Schema
Request message for listing region commitments.
| JSON representation |
|---|
{ "project": string, "region": string, "pageSize": integer, "pageToken": string } |
| Fields | |
|---|---|
project |
Required. Project ID for this request. |
region |
Required. The region of the commitments. |
pageSize |
Optional. The maximum number of commitments to return. |
pageToken |
Optional. A page token received from a previous call to list commitments. |
Output Schema
Response message for listing region commitments.
| JSON representation |
|---|
{
"commitments": [
{
object ( |
| Fields | |
|---|---|
commitments[] |
The list of commitments. |
nextPageToken |
A token that can be sent as |
| JSON representation |
|---|
{ "name": string, "id": string, "status": enum ( |
| Fields | |
|---|---|
name |
Name of the commitment. |
id |
The unique identifier for the commitment. |
status |
The status of the commitment. |
plan |
The plan of the commitment. |
type |
The type of the commitment. |
createTime |
Creation timestamp of the commitment. Uses RFC 3339, where generated output will always be Z-normalized and use 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: |
startTime |
Start timestamp of the commitment. Uses RFC 3339, where generated output will always be Z-normalized and use 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: |
endTime |
End timestamp of the commitment. Uses RFC 3339, where generated output will always be Z-normalized and use 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: |
resources[] |
A list of all the hardware resources of the commitment. |
| JSON representation |
|---|
{ "seconds": string, "nanos": integer } |
| Fields | |
|---|---|
seconds |
Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be between -62135596800 and 253402300799 inclusive (which corresponds to 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z). |
nanos |
Non-negative fractions of a second at nanosecond resolution. This field is the nanosecond portion of the duration, not an alternative to seconds. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be between 0 and 999,999,999 inclusive. |
| JSON representation |
|---|
{
"type": enum ( |
| Fields | |
|---|---|
type |
The type of hardware resource that you want to specify. You can specify any of the following values:
Specify as a separate entry in the list for each individual resource type. |
amount |
The quantity of the hardware resource that you want to commit to purchasing (in a type-dependent unit).
|
acceleratorType |
Name of the accelerator type or GPU resource. Specify this field only when the type of hardware resource is ACCELERATOR. |
Tool Annotations
Destructive Hint: ❌ | Idempotent Hint: ✅ | Read Only Hint: ✅ | Open World Hint: ❌