Skip to main content
Glama
enesjakozh
henihaddad

GCP MCP

by henihaddad
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

list_deployment_manager_deployments

Retrieve a list of Deployment Manager deployments in a specified GCP project to manage and monitor resource configurations effectively.

Instructions

    List Deployment Manager deployments in a GCP project.
    
    Args:
        project_id: The ID of the GCP project to list deployments for
    
    Returns:
        List of Deployment Manager deployments in the specified GCP project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Implementation Reference

  • src/gcp_mcp/gcp_modules/deployment/tools.py:9-21 (handler)
    The handler function for the 'list_deployment_manager_deployments' tool, decorated with @mcp.tool() inside the register_tools function. Includes type hints and docstring serving as schema, and the execution logic (currently a stub).
    @mcp.tool()
def list_deployment_manager_deployments(project_id: str) -> str:
    """
    List Deployment Manager deployments in a GCP project.
    
    Args:
        project_id: The ID of the GCP project to list deployments for
    
    Returns:
        List of Deployment Manager deployments in the specified GCP project
    """
    # TODO: Implement this function
    return f"Not yet implemented: listing deployments for project {project_id}"
  • src/gcp_mcp/server.py:60-60 (registration)
    The call to register the deployment tools module in the main server.py, which triggers the registration of the 'list_deployment_manager_deployments' tool.
    deployment_tools.register_tools(mcp)
  • src/gcp_mcp/server.py:15-15 (registration)
    The import of the deployment tools module in server.py, prerequisite for registration.
    from .gcp_modules.deployment import tools as deployment_tools

Tool Definition Quality

C2.9/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. It mentions listing deployments but doesn't disclose behavioral traits like pagination, rate limits, authentication requirements, or what data is included in the list. This leaves significant gaps for a tool that likely interacts with cloud resources.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized with three sentences: purpose, input, and output. It's front-loaded with the main action, and each sentence adds value without redundancy, though the Args/Returns formatting is slightly verbose.

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?

Given no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on return format (e.g., structure of deployments), error handling, or prerequisites like authentication, which are crucial for a cloud resource 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 description coverage is 0%, but the description adds meaning by explaining that 'project_id' is for specifying the GCP project. This partially compensates, but it doesn't provide details like format or constraints. With one parameter and some added context, it meets the baseline for minimal viability.

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 verb ('List') and resource ('Deployment Manager deployments in a GCP project'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_deployment_details' or other list tools, which would require 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 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 (e.g., 'get_deployment_details' for specific deployments or other list tools for different resources). It only states what it does, not when it's appropriate.

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