Skip to main content
Glama

get-cost-forecast

Forecast Google Cloud Platform project costs for upcoming months to help with budget planning and resource management.

Instructions

Get cost forecast for the current project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoProject ID to get forecast for (defaults to selected project)
monthsNoNumber of months to forecast (default: 3)

Implementation Reference

  • Executes the get-cost-forecast tool by retrieving billing account information for the project (note: does not actually compute a forecast, returns basic billing status).
    } else if (name === "get-cost-forecast") {
      const { projectId, months = 3 } = GetCostForecastSchema.parse(args);
      const targetProject = projectId || selectedProject;
      
      if (!targetProject) {
        return createTextResponse("No project selected. Please select a project first.");
      }
    
      try {
        const billingClient = new CloudBillingClient();
        const [billingInfo] = await billingClient.getProjectBillingInfo({
          name: `projects/${targetProject}`
        });
    
        if (!billingInfo.billingEnabled) {
          return createTextResponse("Billing is not enabled for this project.");
        }
    
        const billingAccount = billingInfo.billingAccountName;
        if (!billingAccount) {
          return createTextResponse("No billing account associated with this project.");
        }
    
        // Get cost forecast using Cloud Billing API
        const [costInfo] = await billingClient.getProjectBillingInfo({
          name: `projects/${targetProject}`
        });
    
        return createTextResponse(JSON.stringify({
          projectId: targetProject,
          billingAccount: billingAccount,
          billingEnabled: costInfo.billingEnabled,
          currency: 'USD'
        }, null, 2));
      } catch (error: any) {
        console.error('Error getting cost forecast:', error);
        if (error.code === 7) {
          return createTextResponse("Error: Cloud Billing API is not enabled. Please enable it in the Google Cloud Console.");
        }
        return createTextResponse(`Error getting cost forecast: ${error.message}`);
      }
  • index.ts:139-156 (registration)
    Registers the 'get-cost-forecast' tool in the list of available tools, including its description and input schema.
    {
      name: "get-cost-forecast",
      description: "Get cost forecast for the current project",
      inputSchema: {
        type: "object",
        properties: {
          projectId: {
            type: "string",
            description: "Project ID to get forecast for (defaults to selected project)",
          },
          months: {
            type: "number",
            description: "Number of months to forecast (default: 3)",
          },
        },
        required: [],
      },
    },
  • Zod schema used for input validation in the get-cost-forecast handler.
    const GetCostForecastSchema = z.object({
      projectId: z.string().optional(),
      months: z.number().optional(),
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Get cost forecast' but doesn't explain what the forecast includes (e.g., breakdowns, accuracy), how it's generated, or any limitations (e.g., data freshness, assumptions). This leaves key behavioral traits unspecified for a forecasting tool.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action ('Get cost forecast') and specifies the scope ('for the current project'), making it easy to parse quickly without unnecessary details.

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 the complexity of cost forecasting and the lack of annotations and output schema, the description is incomplete. It doesn't cover what the forecast returns (e.g., monetary values, time periods), potential errors, or dependencies. For a tool with no structured output and behavioral gaps, this is inadequate.

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 input schema has 100% description coverage, clearly documenting both parameters (projectId and months) with defaults. The description adds no additional meaning beyond the schema, such as explaining what 'cost forecast' entails or how parameters affect the output. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose ('Get cost forecast') and specifies the target ('for the current project'), which is clear but vague. It doesn't distinguish this from potential sibling tools like 'get-billing-budget' or 'get-billing-info', leaving ambiguity about what differentiates a 'forecast' from other billing-related queries.

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. The description implies it's for forecasting costs, but it doesn't specify scenarios (e.g., planning vs. monitoring), prerequisites, or exclusions. Without context, an agent might struggle to choose between this and tools like 'get-billing-budget'.

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

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/RadiumGu/gcp-ops-mcp'

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