Tool: set_instance_machine_type
Sets the machine type for a stopped Google Compute Engine instance to the specified machine type. Requires project, zone, instance name and machine type as input. To get more details about the operation, use the get_zone_operation tool.
The following sample demonstrate how to use curl to invoke the set_instance_machine_type 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": "set_instance_machine_type", "arguments": { // provide these details according to the tool's MCP specification } }, "jsonrpc": "2.0", "id": 1 }' |
Input Schema
Request message for setting machine type.
| JSON representation |
|---|
{ "project": string, "zone": string, "name": string, "machineType": string } |
| Fields | |
|---|---|
project |
Required. Project ID for this request. |
zone |
Required. The zone of the instance. |
name |
Required. Identifier. The instance name. |
machineType |
Required. The machine type of the instance. |
Output Schema
Response message for setting machine type.
| JSON representation |
|---|
{
"errors": {
object ( |
| Fields | |
|---|---|
errors |
Errors encountered during the instance machine type change. |
operationName |
The operation name of the instance machine type change. |
| JSON representation |
|---|
{ "requestId": string, "errors": [ { object ( |
| Fields | |
|---|---|
requestId |
Request identifier generated by the service, which can be used to identify the error in the logs |
errors[] |
Specific error description and codes |
code |
Global error code. Deprecated and ignored. Set custom error codes in ErrorProto.domain and ErrorProto.code instead. |
| JSON representation |
|---|
{
"domain": string,
"code": string,
"arguments": [
string
],
"locationType": enum ( |
| Fields | |
|---|---|
domain |
Error domain. RoSy services can define their own domain and error codes. This should normally be the name of an enum type, such as: gdata.CoreErrorDomain |
code |
Error code in the error domain. This should correspond to a value of the enum type whose name is in domain. See the core error domain in error_domain.proto. |
arguments[] |
Error arguments, to be used when building user-friendly error messages given the error domain and code. Different error codes require different arguments. |
locationType |
|
location |
Location of the error, as specified by the location type. If location_type is PATH, this should be a path to a field that's relative to the request, using FieldPath notation (net/proto2/util/public/field_path.h). Examples: authenticated_user.gaia_id resource.address[2].country |
debugInfo |
Debugging information, which should not be shared externally. |
externalErrorMessage |
A short explanation for the error, which can be shared outside Google. Please set domain, code and arguments whenever possible instead of this error message so that external APIs can build safe error messages themselves. External messages built in a RoSy interface will most likely refer to information and concepts that are not available externally and should not be exposed. It is safer if external APIs can understand the errors and decide what the error message should look like. |
Tool Annotations
Destructive Hint: ✅ | Idempotent Hint: ❌ | Read Only Hint: ❌ | Open World Hint: ❌