Skip to main content
Glama
cortezcristian

Kubecost MCP Server

delete_budget

Remove a budget rule from Kubecost cost management platform to eliminate unwanted spending constraints and maintain accurate cost control policies.

Instructions

Delete a budget rule from Kubecost

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budgetIdYes

Implementation Reference

  • src/index.ts:153-171 (registration)
    MCP tool registration for 'delete_budget', including input schema { budgetId: z.string() } and inline handler that calls kubecostClient.deleteBudget(budgetId) and returns formatted response
    this.tool(
      'delete_budget',
      'Delete a budget rule from Kubecost',
      { budgetId: z.string() },
      async ({ budgetId }) => {
        try {
          await this.kubecostClient.deleteBudget(budgetId);
          return {
            isError: false,
            content: [{ type: 'text', text: `Budget with ID ${budgetId} deleted successfully` }]
          };
        } catch (error) {
          return {
            isError: true,
            content: [{ type: 'text', text: error instanceof Error ? error.message : String(error) }]
          };
        }
      }
    );
  • Input schema for delete_budget tool using Zod validation
    { budgetId: z.string() },
  • KubecostClient helper method that performs the HTTP DELETE request to delete the budget via Kubecost API
    async deleteBudget(budgetId: string): Promise<void> {
      await this.client.delete(`/model/budget/${budgetId}`);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention permissions needed, whether deletion is reversible, side effects, error conditions, or rate limits—critical for a destructive operation.

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—front-loaded and appropriately sized for the tool's scope. Every word earns its place without redundancy.

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 tool's destructive nature, no annotations, 0% schema coverage, and no output schema, the description is incomplete. It fails to address risks, prerequisites, or expected outcomes, making it inadequate for safe agent invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no meaning beyond the schema. It doesn't explain what budgetId represents, its format, or where to find it (e.g., from list_budgets), leaving the single required parameter undocumented.

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

Purpose5/5

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

The description clearly states the specific action ('Delete') and target resource ('a budget rule from Kubecost'), distinguishing it from sibling tools like create_budget, update_budget, and list_budgets. It uses precise verb+resource phrasing without tautology.

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 like update_budget or delete operations in other contexts. The description lacks explicit when/when-not instructions or references to sibling tools, leaving usage context implied at best.

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/cortezcristian/kubecost-mcp'

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