Skip to main content
Glama
henihaddad

GCP MCP

by henihaddad
OverviewSchemaRelated ServersScoreDiscussions
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

Tool Definition Quality

B3.1/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 burden of behavioral disclosure. While 'Get details' implies a read-only operation, the description doesn't specify authentication requirements, rate limits, error conditions, or what format the returned details will be in. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 well-structured and appropriately sized. It uses a clear three-part format (purpose, args, returns) with no redundant information. Every sentence serves a distinct purpose, making it easy to parse and understand quickly.

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?

Given the tool's moderate complexity (2 required parameters, no output schema, no annotations), the description provides a basic but incomplete picture. It covers the purpose and parameters adequately but lacks behavioral context, usage guidance relative to siblings, and details about the return format. For a read operation with no output schema, more information about what 'Details' includes would be helpful.

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 0%, so the schema provides no parameter descriptions. The description compensates by listing both parameters with brief explanations ('The ID of the GCP project', 'The name of the deployment to get details for'), which adds meaningful context beyond the bare schema. However, it doesn't provide format examples, constraints, or validation rules.

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?

The description clearly states the tool's purpose with a specific verb ('Get details') and resource ('Deployment Manager deployment'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'list_deployment_manager_deployments', which might cause confusion about when to use one versus the other.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling 'list_deployment_manager_deployments' tool or clarify that this is for retrieving details of a specific deployment rather than listing multiple deployments. No context or exclusions are provided.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/henihaddad/gcp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server