Skip to main content
Glama

Show balance and credential limits

get_balance
Read-onlyIdempotent

Read-only, free. Show the prepaid ipvolt balance (available and held) of the credential's account and, for an API key, its access level, daily spending limit, what it spent today and what it can still spend today; for an agent token, its permissions and spending cap.

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.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the description isn't the sole source of the safety profile. It still adds real value beyond them: the call is free, it scopes to "the credential's account", and the returned data differs between an API key (access level, daily limit, spent today, remaining) and an agent token (permissions, spending cap).

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?

Front-loaded with the two facts an agent most needs (read-only, free), then a compact enumeration. The single semicolon-chained sentence is dense but every clause names a distinct returned field or credential-type branch; nothing is 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?

With no output schema, the description carries the burden of describing return values, and it does so field-by-field for both credential types. Minor gaps remain: no mention of currency/units, of what happens when the credential lacks an account, or of staleness of the "today" figures.

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?

There are zero parameters, which is the baseline-4 case. The description usefully clarifies why: the account is derived from the calling credential rather than passed in, so the agent knows not to hunt for an account identifier.

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 and resource ("Show the prepaid ipvolt balance") with the exact fields returned, and branches the return content by credential type (API key vs agent token). It is clearly distinguishable from the sibling rental/traffic/proxy tools, which mutate or enumerate resources rather than report account state.

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?

"Read-only, free" gives the agent clear context for choosing this over any mutating sibling (buy_traffic_pack, rent_proxy, rotate_ip) when it only needs status. No explicit when-not or named alternative is given, but for a zero-parameter getter the selection decision is nearly trivial.

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