Skip to main content
Glama

Start a task budget

budget_start

Start a task budget with a max USD cost and time limit; billed tool calls spend from it, calls that exceed it are refused before billing, and the operator's ceiling still caps it.

Instructions

Start a task budget, max_cost_usd at list prices and time_limit_s from now, that every billed tool spends from; a call that does not fit is refused before it bills. It replaces the previous one, and the operator's ceiling still caps it.

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": {
      "max_cost_usd": "<max_cost_usd>",
      "time_limit_s": "<time_limit_s>"
    },
    "name": "budget_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_cost_usdYesThe most to spend, in US dollars, at estimated list prices.
time_limit_sYesThe most seconds the task may run billed calls, from now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A3.6/5.0
Behavior3/5

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

Adds genuine behavior beyond the annotations: overspending calls are refused before they bill, an existing budget is overwritten, and the operator ceiling still applies. However, it does not say what happens to already-billed spend when replaced, nor whether the refusal surfaces as an error to the caller.

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?

One front-loaded sentence with no filler, and the key budget semantics come first. The comma/semicolon chaining makes it denser than necessary, but every clause carries information.

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?

For a two-parameter mutation with full schema coverage and safety annotations, the description covers cost basis, clock start, replacement, and the enforcement mechanism. It leaves a modest gap around the interaction between an existing budget and a replacement, which an agent might need.

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 coverage is 100%, so both parameters are already documented with units and exclusiveMinimum constraints. The description echoes that framing ('at list prices', 'from now') without adding format or edge-case detail, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Start a task budget') and immediately defines what the two inputs mean in operation ('max_cost_usd at list prices and time_limit_s from now'). It does not name a sibling such as budget_status, so the differentiation from alternatives is left implicit.

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?

Implies the trigger clearly: this establishes the pool that 'every billed tool spends from', so it belongs before billed work. It also warns that calling it again 'replaces the previous one', which is a real usage condition, but it never says when not to use it or points to budget_status for inspection.

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