Skip to main content
Glama
agentisend

agentisend

Get this key’s budget

get_agent_budget
Read-onlyIdempotent

Check how much send budget remains for the current API key, when it resets, and the per-minute ceiling before a batch or after a budget-exceeded refusal.

Instructions

Purpose: see how much of this key's send budget is left, when it refills, and its per-minute ceiling. Read it before a batch, and after an agent_budget_exceeded refusal. NOT for: changing any of it. Raising is the account owner's. Returns: budget, consumed, remaining, the period and when it resets, and the per-minute ceiling with its current window.

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_agent_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
periodNo
remainingNo
api_key_idNoIdentifier.
api_key_nameNo
period_resets_atNoISO 8601 time.
budget_per_periodNoNull: metered but unlimited.
period_started_atNoISO 8601 time.
consumed_in_periodNo
consumed_in_windowNo
rate_ceiling_per_minuteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context: it discloses what state is inspectable and that raising the budget is out of scope for this key. It stops short of noting rate limits on the call itself or permission requirements, but that is minor here.

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?

Front-loaded with labeled sections (Purpose / NOT for / Returns) and every sentence earns its place. The scoping constraint and the invocation triggers are stated with no filler.

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?

An output schema exists, so the description does not need to enumerate return fields, yet it lists them anyway ('budget, consumed, remaining, period, reset, per-minute ceiling'). That is mild redundancy rather than a gap; the definition is otherwise complete for a parameterless read tool.

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 the baseline is 4; schema coverage is 100% and there is nothing for the description to compensate for. No parameter-level ambiguity exists.

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+resource: reading this key's send budget, refill time, and per-minute ceiling. It is clearly distinguishable from set_limit (which changes limits) and send_batch (which consumes budget), and the 'NOT for' line sharpens the boundary further.

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?

Gives explicit when-to-use triggers ('before a batch', 'after an agent_budget_exceeded refusal') and an explicit when-not ('changing any of it'), plus names who owns the alternative action (the account owner). Nothing about invocation timing is left to inference.

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