Skip to main content
Glama

get_account_balance

Read-only

Check the CapSolver account balance without creating a paid solve task to verify available credits before running CAPTCHA workflows.

Instructions

Check the CapSolver account balance without creating a paid solve task.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a non-mutating operation. The description adds useful context by saying no paid solve task is created, reinforcing that there is no billing side effect. It does not add further behavioral detail such as auth requirements or rate limits, but none is essential given the annotations and 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 definition is a single front-loaded sentence with no wasted wording. It states the purpose and the key non-side-effect immediately.

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?

For a zero-parameter, read-only balance tool with annotations and an output schema, the description is nearly complete. The only missing context is how this differs from the sibling get_balance, which would help an agent choose correctly between the two.

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?

This tool has zero parameters, so there is no parameter semantics burden. The description does not need to explain inputs, and the baseline for zero-parameter tools applies.

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 states a specific verb and resource: check the CapSolver account balance. It also clarifies that this does not create a paid solve task, which distinguishes it from task-creation tools. However, it does not distinguish this tool from the sibling get_balance, leaving ambiguity about why two balance-related tools exist.

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?

The phrase 'without creating a paid solve task' implies this is appropriate when the caller wants to inspect balance without incurring solve costs. Yet there is no explicit guidance on when to choose this over get_balance or other account-related siblings, so the usage boundary remains partially inferred.

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