Skip to main content
Glama

Get the balance

get_balance
Read-only

Use this when the user asks how much money is left, or before a paid call to check that it can be covered. Returns the organization's balance in US dollars, the amount set aside for calls in progress, what new calls can use, whether auto-recharge is on, and today's spend. Free. It cannot add funds: that is done by a person in the outbound.dev console.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the read-only, non-destructive annotations, the description discloses that the call is free and that it cannot mutate the balance. It also enumerates the returned balance components, giving the agent useful behavioral context even without an output schema.

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?

The description is front-loaded with the primary use case, then the return contents, then the limitation. Every sentence adds distinct value: usage trigger, output fields, cost, and the fact that funding happens elsewhere.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so in detail. The usage trigger, cost, and limitation together make the definition complete for this simple, zero-parameter 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 has zero parameters, so there is no parameter semantics to clarify. The baseline for a parameterless tool is 4; the description correctly does not invent parameter details.

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?

The description states a specific verb and resource—getting the organization's balance—and lists the exact information returned (USD balance, reserved funds, available funds, auto-recharge status, today's spend). It also distinguishes the tool's scope by explicitly saying it cannot add funds, which prevents confusion with any funding-related action.

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?

It gives explicit when-to-use guidance: when the user asks how much money is left, or before a paid call to verify coverage. It also supplies a clear when-not route by stating that adding funds is done by a person in the outbound.dev console, leaving little ambiguity.

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