Skip to main content
Glama

tokmeter_budget_alert

Read-only

Monitor whole-account AI spend against daily, weekly, and monthly budgets, returning usage status, projected overruns, and hours left before budgets run out.

Instructions

Whole-account budget status: pass a daily budget (required) and optionally weekly and monthly ones. For each: spend so far, percent used, projected end-of-period spend at the current hourly burn rate, hours left before the budget runs out, and a status of OK (<80%), WARNING (80–99%) or OVER BUDGET. Covers all providers and projects; to check a budget for one project or provider, use tokmeter_budget. Nothing is stored or scheduled: it reports on demand.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "daily_budget": "<daily_budget>"
    },
    "name": "tokmeter_budget_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
daily_budgetYesDaily budget in USD
weekly_budgetNoWeekly budget in USD
monthly_budgetNoMonthly budget in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.19.3

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds meaningful behavior beyond that: it reports spend, percent used, projected spend, hours remaining, and status thresholds. It also clarifies that nothing is stored or scheduled and that results cover all providers and projects.

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 front-loaded with the account-level scope, then states required and optional inputs, then enumerates outputs and status thresholds. It is dense but every sentence contributes useful selection or interpretation context.

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?

Even without an output schema, the description explains the returned metrics and status categories, and it clarifies global versus scoped budget behavior. For a read-only reporting tool, an agent has enough information to select and invoke 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 schema already documents each budget parameter as USD with required/optional status. The description restates the required/optional distinction but adds little parameter-level meaning beyond the schema.

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 states a specific resource and scope: whole-account budget status covering daily, weekly, and monthly budgets, with defined output fields and thresholds. It also explicitly distinguishes itself from the sibling tool for single-project or single-provider budgets.

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

Usage Guidelines5/5

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

It clearly says daily_budget is required while weekly_budget and monthly_budget are optional. It also gives an explicit alternative: use tokmeter_budget when checking a budget for one project or provider, which is exactly the routing guidance an agent needs.

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