Skip to main content
Glama

get_billing_info

Retrieve billing details for a specific Google Cloud Platform project by providing its project ID. Simplifies cost management and transparency for GCP resources.

Instructions

    Get billing information for a GCP project.
    
    Args:
        project_id: The ID of the GCP project to get billing information for
    
    Returns:
        Billing information for the specified GCP project
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Implementation Reference

  • The get_billing_info tool handler: fetches GCP project billing info using CloudBillingClient, formats and returns details or errors.
        @mcp.tool()
        def get_billing_info(project_id: str) -> str:
            """
            Get billing information for a GCP project.
            
            Args:
                project_id: The ID of the GCP project to get billing information for
            
            Returns:
                Billing information for the specified GCP project
            """
            try:
                try:
                    from google.cloud import billing_v1
                except ImportError:
                    return "Error: The Google Cloud billing library is not installed. Please install it with 'pip install google-cloud-billing'."
                
                # Initialize the Cloud Billing client
                billing_client = billing_v1.CloudBillingClient()
                
                # Get the billing account for the project
                project_name = f"projects/{project_id}"
                billing_info = billing_client.get_project_billing_info(name=project_name)
                
                # If billing is enabled, get more details about the billing account
                if billing_info.billing_account_name:
                    billing_account = billing_client.get_billing_account(
                        name=billing_info.billing_account_name
                    )
                    
                    # Initialize the Cloud Catalog client to get pricing information
                    catalog_client = billing_v1.CloudCatalogClient()
                    
                    # Format the response
                    return f"""
    Billing Information for GCP Project {project_id}:
    
    Billing Enabled: {billing_info.billing_enabled}
    Billing Account: {billing_info.billing_account_name}
    Display Name: {billing_account.display_name}
    Open: {billing_account.open}
    """
                else:
                    return f"Billing is not enabled for project {project_id}."
            except Exception as e:
                return f"Error getting billing information: {str(e)}"
  • Input schema: project_id (str); Output: str (formatted billing info). Defined via type hints and docstring.
    def get_billing_info(project_id: str) -> str:
        """
        Get billing information for a GCP project.
        
        Args:
            project_id: The ID of the GCP project to get billing information for
        
        Returns:
            Billing information for the specified GCP project
        """
  • Module-level register_tools(mcp) defines and registers the get_billing_info tool via @mcp.tool() decorator.
    def register_tools(mcp):
        """Register all billing tools with the MCP server."""
        
        @mcp.tool()
        def get_billing_info(project_id: str) -> str:
            """
            Get billing information for a GCP project.
            
            Args:
                project_id: The ID of the GCP project to get billing information for
            
            Returns:
                Billing information for the specified GCP project
            """
            try:
                try:
                    from google.cloud import billing_v1
                except ImportError:
                    return "Error: The Google Cloud billing library is not installed. Please install it with 'pip install google-cloud-billing'."
                
                # Initialize the Cloud Billing client
                billing_client = billing_v1.CloudBillingClient()
                
                # Get the billing account for the project
                project_name = f"projects/{project_id}"
                billing_info = billing_client.get_project_billing_info(name=project_name)
                
                # If billing is enabled, get more details about the billing account
                if billing_info.billing_account_name:
                    billing_account = billing_client.get_billing_account(
                        name=billing_info.billing_account_name
                    )
                    
                    # Initialize the Cloud Catalog client to get pricing information
                    catalog_client = billing_v1.CloudCatalogClient()
                    
                    # Format the response
                    return f"""
    Billing Information for GCP Project {project_id}:
    
    Billing Enabled: {billing_info.billing_enabled}
    Billing Account: {billing_info.billing_account_name}
    Display Name: {billing_account.display_name}
    Open: {billing_account.open}
    """
                else:
                    return f"Billing is not enabled for project {project_id}."
            except Exception as e:
                return f"Error getting billing information: {str(e)}"
  • Imports the billing tools module (containing get_billing_info) for registration.
    from .gcp_modules.billing import tools as billing_tools
  • Calls register_tools on billing_tools module to register get_billing_info with the MCP server.
    billing_tools.register_tools(mcp)
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. It states the tool retrieves billing information but does not describe traits like required permissions, rate limits, error handling, or output format. For a read operation with zero annotation coverage, this is a significant gap in transparency.

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 concise and well-structured: a clear purpose statement followed by Args and Returns sections. However, the Returns section is vague ('Billing information') and could be more informative, slightly reducing efficiency.

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 a read operation with potential complexity (billing data), the description is incomplete. It lacks details on authentication, permissions, data format, and error cases, making it inadequate for safe and effective use by an AI agent.

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?

The description adds minimal semantics: it explains that 'project_id' is 'The ID of the GCP project to get billing information for.' With 0% schema description coverage and only one parameter, this provides basic meaning but does not elaborate on format (e.g., project ID structure) or constraints. The baseline is appropriate given the low parameter count.

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: 'Get billing information for a GCP project.' It specifies the verb ('Get') and resource ('billing information'), and the context ('for a GCP project') is clear. However, it does not explicitly differentiate from sibling tools like 'get_gcp_project_details' or other 'get_' 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. It does not mention prerequisites (e.g., authentication), exclusions, or related tools. With many sibling tools available, this lack of context leaves the agent without usage direction.

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