Skip to main content
Glama

Get cost budgets

get_cost_budgets
Read-only

Read the monthly cost budgets in scope - the current project's, or one project's or the whole organisation's with project_id - largest first, each with its month as of now in the budget's own currency: spent so far, the projected month end at the current pace, the hour that pace crosses the budget, the percent of the budget, and where the month lands once the changes already approved or running have landed. status is under, approaching (past the notify threshold), crossing, over, or unknown - unknown means no cluster in scope is priced this month and the figures are null, which is unknown spend, not zero. Read-only; read this before set_cost_budget or delete_cost_budget.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cost_budgets"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoUUID of a project to read, or all for the whole organisation. Leave it out to read the project the conversation or token is in (the whole organisation while the organisation has no projects). list_projects has the ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / project_id
      Added value: +{
      +  "description": "UUID of a project to read, or all for the whole organisation. Leave it out to read the project the conversation or token is in (the whole organisation while the organisation has no projects). list_projects has the ids.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds substantial behavior: values are in the budget's own currency, month as of now, largest-first ordering, and the full status taxonomy (under, approaching, crossing, over, unknown). Crucially it explains that unknown means no cluster in scope is priced and figures are null — unknown spend, not zero — which prevents a serious misreading.

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?

Front-loaded with verb, scope, and ordering before the return-field list; each clause carries information (status meanings, currency, null semantics). It is a single very dense sentence, so readability suffers slightly, but nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the return-value burden and does so thoroughly: spent, projected month end, crossing hour, percent, post-change landing, plus status values and their meaning. Scope defaults and the unknown-vs-zero distinction round out what an agent needs to call and interpret it correctly.

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% and the single parameter already documents the UUID/'all' values and the default-to-context behavior. The description restates the scope meaning ('one project's or the whole organisation's with project_id') but adds no syntax or edge-case detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Read the monthly cost budgets') plus scope variants (current project, one project via project_id, or whole organisation) and ordering ('largest first'). It also names the sibling write tools it is not (set_cost_budget, delete_cost_budget), so an agent can distinguish it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes usage: 'read this before set_cost_budget or delete_cost_budget' and explains that omitting project_id reads the conversation's project. It stops short of stating when not to use it (e.g. per-namespace or historical budget data, which sibling cost tools may cover), so it is strong but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.