Skip to main content
Glama

Show the budget

budget_status
Read-only

Retrieve dollars spent, funds reserved for running calls, remaining budget and time, plus any operator-set ceiling. It calls nothing and helps monitor spend before or during agent runs.

Instructions

Where the current budget stands: dollars spent, reserved for calls still running and left, and seconds elapsed and left; and the operator's ceiling, if one is set. Free: it calls nothing.

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": "budget_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: the call itself is free and invokes nothing downstream, and the reported figures include amounts reserved for calls still running, which explains why spent plus left may not sum to the ceiling. It does not state units or formatting for the time values, which is a minor residual gap.

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?

The content is front-loaded — the subject and the reported fields come first, with the cost reassurance as a short trailing clause. The single semicolon-chained sentence is dense but every clause corresponds to a distinct returned value, so nothing is padding. It could be broken into shorter units for faster scanning.

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

Completeness4/5

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

With no parameters, no output schema, and only two annotations, the description carries most of the informational load and does it well by enumerating each reported figure and noting the optional ceiling. The only shortfall is the absence of return format or unit details, which matters slightly more here precisely because no output schema exists to supply them.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter meaning is required or missing.

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 names a specific resource — the current budget — and enumerates exactly what it reports: dollars spent, dollars reserved for in-flight calls, dollars left, seconds elapsed and left, plus the operator's ceiling. An agent can tell this is a read-only status report rather than a budget mutation. It does not explicitly distinguish itself from the sibling budget_start, which is the only thing keeping it from a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent infers it should call this to check remaining budget or elapsed time, likely before or after cost-incurring tools like call_vendor or budget_start. There is no explicit when-to-use statement, no exclusion, and no named alternative, so the agent must infer the routing decision from the field list alone.

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