Skip to main content
Glama
Sign In
Google Cloud MCP Server

Google Cloud MCP Server

by iamishaan24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Project ID

gcp-utils-get-project-id

Identify the active Google Cloud project ID and review recent project history to confirm or switch project context.

Instructions

Get the current Google Cloud project ID and recent project history

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gcp-utils-get-project-id"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral context. 'Get' communicates a read operation and names the returned data, but it does not disclose whether it depends on local gcloud configuration, requires authentication, or whether it has any side effects. It is adequate but thin.

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?

A single sentence that front-loads the main action and resource, with no filler or redundant restatement of the name.

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

Completeness4/5

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

For a zero-parameter utility, the description is largely complete: it states the two outputs (current project ID and history). The term 'recent project history' is slightly vague, but the absence of parameters and output schema makes this a low-risk gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters, so the baseline is 4. The schema is fully trivial, and the description accurately describes what the call produces without needing to document input semantics.

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') with a clear resource ('current Google Cloud project ID') and adds the distinct 'recent project history' scope. The qualifier 'current' differentiates this from sibling gcp-list-project-ids, which would list all project IDs.

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

Usage Guidelines3/5

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

The 'current' wording implies choosing this tool when the active/configured project is needed, but there is no explicit statement of when to use it versus gcp-list-project-ids or gcp-utils-set-project-id. Usage context is implied rather than 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