Skip to main content
Glama

list_agent_budgets

Read-onlyIdempotent

Retrieve current USD spending caps and balances for all tenant agents in a single call, including BYOK usage, to monitor AI agent costs and budget limits.

Instructions

Get current USD spending caps and balances for all tenant agents in one call. Includes BYOK usage.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this read-only, idempotent, and non-destructive, so the safety profile is covered elsewhere. The description adds genuinely useful context beyond that - the values are 'current' (live, not cached) and include BYOK usage, which affects how the numbers should be interpreted. It does not cover result-size behavior or whether platform and BYOK spend are broken out separately.

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?

Two short sentences with no filler, and the scope-defining phrase 'in one call' is front-loaded. Every clause contributes either scope or data-composition information.

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

Completeness3/5

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

With no output schema, the description is the only source of return-value information, and it only loosely sketches the shape ('caps and balances') without saying whether each agent yields one or two figures or how BYOK versus platform spend is represented. For a zero-parameter bulk read this is adequate to call correctly but leaves the response structure to discovery.

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 no parameters, so there is no semantic gap to fill and the baseline is 4 by rule. The description appropriately spends no words on argument syntax.

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 pairs a specific verb ('Get') with a specific resource ('current USD spending caps and balances for all tenant agents'), and the phrase 'in one call' signals batch scope versus the singular get_agent_budget sibling. It stops short of naming that sibling explicitly, so the differentiation is implied rather than stated.

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?

'for all tenant agents in one call' implies the use case is a bulk budget view, which is reasonable guidance for choosing this over a single-agent fetch. However, there is no explicit when-to-use or when-not-to-use statement and no reference to get_agent_budget for per-agent lookups, leaving the agent to infer the boundary.

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

Deploy Server

Other Tools