Skip to main content
Glama

check_balance

Read the caller's token wallet balance (available, reserved, total, average daily spend), active plan code, and the checks that plan allows (for example whether smtp or catchall are available). Use it before a large submit_batch to confirm the balance and which checks the plan allows; for spending history use list_transactions, and for verification counts by verdict use get_usage. Requires the billing:read scope.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does well: 'Read' signals a non-mutating operation, the returned value set is enumerated, and the required billing:read scope is disclosed — a genuine auth prerequisite an agent cannot infer elsewhere. It stops short of 5 by not mentioning rate limits or what happens when the scope is missing.

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 sentences, both dense with actionable content: the first says what comes back, the second says when to call it and what to call instead. The pre-call use case is front-loaded ahead of the sibling routing, and nothing is padding.

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?

No output schema exists, so the description must describe return values — and it does, listing the balance components, plan code, and plan-gated checks with a concrete example (smtp, catchall). Combined with the auth scope and sibling routing, nothing an agent needs to call this zero-parameter read correctly is missing.

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 (empty object schema), so there is no parameter meaning to convey; the baseline for a parameterless tool applies. The description wisely spends its budget on return semantics instead of restating the empty 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?

States a specific verb (Read) and resource (caller's token wallet balance), and enumerates the exact return fields: available, reserved, total, average daily spend, plan code, and permitted checks. It also distinguishes itself from near-neighbors by naming list_transactions and get_usage as the tools for other questions.

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 an explicit trigger ('Use it before a large submit_batch to confirm the balance and which checks the plan allows') and routes two adjacent needs to the correct alternatives: spending history to list_transactions, verification counts by verdict to get_usage. Both when-to-use and when-not-to-use are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources