Skip to main content
Glama

get_budget_details

Retrieve AWS Budgets with status, limits, and current spend to monitor and manage cloud costs effectively.

Instructions

Lists all AWS Budgets along with their status, limits, and current spend.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYesThe AWS Account ID (required for Budgets).

Implementation Reference

  • Handler function that fetches AWS Budget details using AWS SDK's BudgetsClient and DescribeBudgetsCommand, processes the response to include budget name, limits, spends, type, and last updated time.
    if (name === "get_budget_details") {
        const accountId = (args as any).account_id;
        const command = new DescribeBudgetsCommand({ AccountId: accountId, MaxResults: 100 });
        const response = await budgetsClient.send(command);
    
        const budgets = response.Budgets?.map(b => ({
            BudgetName: b.BudgetName,
            Limit: b.BudgetLimit?.Amount + " " + b.BudgetLimit?.Unit,
            CurrentSpend: b.CalculatedSpend?.ActualSpend?.Amount + " " + b.CalculatedSpend?.ActualSpend?.Unit,
            ForecastedSpend: b.CalculatedSpend?.ForecastedSpend?.Amount + " " + b.CalculatedSpend?.ForecastedSpend?.Unit,
            BudgetType: b.BudgetType,
            LastUpdated: b.LastUpdatedTime
        })) || [];
    
        return { content: [{ type: "text", text: JSON.stringify(budgets, null, 2) }] };
    }
  • Input schema definition for the get_budget_details tool, specifying the required 'account_id' parameter.
        name: "get_budget_details",
        description: "Lists all AWS Budgets along with their status, limits, and current spend.",
        inputSchema: {
            type: "object",
            properties: {
                account_id: { type: "string", description: "The AWS Account ID (required for Budgets)." }
            },
            required: ["account_id"]
        }
    },
  • src/index.ts:235-244 (registration)
    Tool registration in the ListTools response, defining name, description, and schema.
        name: "get_budget_details",
        description: "Lists all AWS Budgets along with their status, limits, and current spend.",
        inputSchema: {
            type: "object",
            properties: {
                account_id: { type: "string", description: "The AWS Account ID (required for Budgets)." }
            },
            required: ["account_id"]
        }
    },
  • Initialization of the AWS BudgetsClient used by the tool handler.
    const budgetsClient = new BudgetsClient({});
  • Import of AWS SDK Budgets client and DescribeBudgetsCommand used in the tool.
    import { BudgetsClient, DescribeBudgetsCommand } from "@aws-sdk/client-budgets";
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 describes a read-only operation ('Lists') but does not mention permissions, rate limits, pagination, or response format. The description is minimal and lacks critical behavioral details needed for safe and effective use.

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 that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to understand quickly. Every part of the sentence contributes to clarity.

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 complexity (a read operation with one parameter) and lack of annotations and output schema, the description is minimally complete. It covers the basic purpose but misses behavioral details like permissions or response structure. For a tool with no annotations, it should provide more context to be fully 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 100%, with the single parameter 'account_id' fully documented in the schema. The description does not add any parameter-specific information beyond what the schema provides, such as format examples or constraints. The baseline score of 3 reflects adequate coverage by the schema alone.

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: 'Lists all AWS Budgets along with their status, limits, and current spend.' It specifies the verb ('Lists'), resource ('AWS Budgets'), and scope ('all'), but does not explicitly differentiate from sibling tools like 'get_cost_breakdown' or 'get_cost_forecast', which are related but not direct alternatives for listing budgets.

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 sibling tools or contexts where this tool is preferred, such as for budget monitoring versus cost analysis. Usage is implied by the purpose but lacks explicit when/when-not instructions.

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/bhaveshopss/MCP-server'

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