Skip to main content
Glama
henihaddad

GCP MCP

by henihaddad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_deployment_details

Retrieve detailed information about a specific Google Cloud Platform Deployment Manager deployment, including project ID and deployment name, for comprehensive resource insights.

Instructions

    Get details of a specific Deployment Manager deployment.
    
    Args:
        project_id: The ID of the GCP project
        deployment_name: The name of the deployment to get details for
    
    Returns:
        Details of the specified deployment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deployment_nameYes
project_idYes

Implementation Reference

  • src/gcp_mcp/gcp_modules/deployment/tools.py:23-36 (handler)
    The main handler function for the 'get_deployment_details' tool. It is decorated with @mcp.tool() which also handles registration. Includes type annotations for parameters and return type, serving as the input/output schema, and a docstring describing the tool.
    @mcp.tool()
def get_deployment_details(project_id: str, deployment_name: str) -> str:
    """
    Get details of a specific Deployment Manager deployment.
    
    Args:
        project_id: The ID of the GCP project
        deployment_name: The name of the deployment to get details for
    
    Returns:
        Details of the specified deployment
    """
    # TODO: Implement this function
    return f"Not yet implemented: getting details for deployment {deployment_name} in project {project_id}"
  • src/gcp_mcp/server.py:60-60 (registration)
    The call to deployment_tools.register_tools(mcp) that triggers the registration of the 'get_deployment_details' tool (along with other deployment tools) to the MCP server.
    deployment_tools.register_tools(mcp)
  • src/gcp_mcp/server.py:15-15 (registration)
    Import of the deployment tools module, which contains the 'get_deployment_details' implementation and its register_tools function.
    from .gcp_modules.deployment import tools as deployment_tools

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It only says 'Get details' without describing side effects, permissions required, error behaviors, or return format specifics. While 'Get' implies a read operation, this is not explicitly stated, and no additional behavioral context is added.

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 concise and well-structured with clear Args and Returns sections. No unnecessary words or repetition, and it efficiently conveys the essential information in a few lines.

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 getter tool, the description covers the core purpose and parameters. However, it lacks details about the return value structure (no output schema), does not mention potential error cases, and provides no usage guidance relative to siblings. It is adequate but leaves room for improvement.

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 schema has 0% description coverage, but the description compensates with an Args section explaining both parameters: 'project_id' as the GCP project ID and 'deployment_name' as the deployment name. This adds meaningful context beyond the schema's bare labels, though it lacks format constraints or examples.

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 clearly states the tool gets details of a specific Deployment Manager deployment, using a specific verb ('Get') and resource ('Deployment Manager deployment'). It distinguishes from sibling tools like list_deployment_manager_deployments by emphasizing 'specific', making the purpose unambiguous.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or comparison to other tools like list_deployment_manager_deployments. The usage context is only implied by the name, not explained.

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

Related Tools