Skip to main content
Glama
Sign In
google-cloud-console-mcp

google-cloud-console-mcp

by kutleloove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get GCP project

gcp_get_project

Fetch details for a single Google Cloud project by project ID, or use the GOOGLE_CLOUD_PROJECT environment variable when no ID is provided.

Instructions

Fetches details of a single GCP project.

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_get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdNoGCP project id; defaults to GOOGLE_CLOUD_PROJECT env var if omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It only says 'fetches details' and doesn't disclose what details are returned, whether it requires specific permissions, whether it returns error if project doesn't exist, or any other behavioral trait. This is inadequate for a read tool with no annotations.

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?

One short sentence with zero waste, front-loading the essential action and scope. Perfectly concise for a simple tool.

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

Completeness2/5

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

With no annotations and no output schema, the description should explain what 'details' includes or at least confirm it's a read-only operation. It doesn't, leaving the agent with insufficient behavioral context to confidently invoke the tool.

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 coverage is 100%, so the schema already fully documents the projectId parameter including its default. The description adds no parameter meaning beyond the schema, making baseline 3 appropriate.

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?

Specific verb (fetches) and resource (single GCP project) are clearly stated, differentiating it from gcp_list_projects which lists multiple. However, it doesn't explicitly name the sibling, so it falls short of a 5.

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 word 'single' implies you use this when you know the project ID and need details for one project, as opposed to listing. But there's no explicit when-to-use or exclusion guidance, leaving it 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