Skip to main content
Glama
Sign In
CaptchaAI MCP Server

CaptchaAI MCP Server

Official
by CaptchaAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Balance

get_balance
Read-only

Retrieves the CaptchaAI account balance from the API so you can check remaining capacity before solving CAPTCHA challenges.

Instructions

Get the CaptchaAI account balance as returned by the API.

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and an output schema exists, so the description does not need to explain return values. The description adds almost no behavioral context beyond confirming the API-backed balance read, but for a simple zero-parameter read tool that is minimally acceptable.

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?

The description is a single front-loaded sentence with no unnecessary preamble. The phrase 'as returned by the API' adds little value but does not meaningfully bloat the description.

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?

Given the zero-parameter schema, read-only annotation, and output schema, the description is complete enough for an agent to call it correctly. It could mention authentication or balance units, but those gaps are minor for this simple 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 takes zero parameters, so there are no parameter semantics to explain. Baseline 4 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: getting the CaptchaAI account balance. It distinguishes the tool from unrelated siblings like get_threads and solve_captcha, though it does not clarify what 'balance' means (credits, currency, etc.).

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?

Usage is implied by the purpose—call it when you need the account balance—but there is no explicit when-to-use or when-not-to-use guidance. No alternatives are named, though none of the siblings appear to overlap.

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