Skip to main content
Glama
Sign In
Google Cloud MCP Server

Google Cloud MCP Server

by iamishaan24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Instance IP and SSH Command

gcp-compute-get-instance-ip

Retrieve external IP addresses for a Compute Engine VM and get suggested SSH commands.

Instructions

Fetch external IP(s) for a VM and provide suggested SSH commands

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "zone": "<zone>"
    },
    "name": "gcp-compute-get-instance-ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesInstance name
zoneYesZone of the instance (e.g., us-central1-a)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only describes the happy path and does not explain behavior for stopped instances, missing external IPs, multiple network interfaces, authentication requirements, or the exact output format.

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 a single concise sentence with no filler. The core action and expected output are front-loaded and easy to parse.

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?

For a simple two-parameter read-oriented tool, the description adequately names the input, target resource, and output. However, with no annotations and no output schema, it lacks edge-case behavior and differentiation from similar sibling tools, leaving the agent to infer important operational details.

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 both parameters are already documented in the input schema. The description adds little beyond 'for a VM', which matches the baseline expectation but provides no extra semantic value.

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?

States a specific verb and resource: fetch external IP(s) for a VM and provide suggested SSH commands. It is clear about the tool's intent but does not explicitly distinguish itself from the closely named sibling get-compute-vm-ip, which appears to serve a similar IP lookup purpose.

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?

No when-to-use or when-not-to-use guidance is provided, and no alternative tools are referenced. The intended usage is only implied by the tool description rather than explicitly stated.

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

Deploy Server

Other Tools