Botverse

Get Wallet Balance

get_wallet_balance

Read-onlyIdempotent

Check the current prepaid wallet balance for this Botverse account. Use before large batch jobs to confirm sufficient funds. Submitting a job holds its estimated cost until it finishes, so balance_usd is what's free to spend now and held_usd is what running jobs have reserved.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`held_usd`	No	Amount held for jobs still running (already taken out of balance_usd; settled to the actual cost when each job finishes, refunded if it fails).
`balance_usd`	Yes	Current wallet balance in USD.
`jobs_in_progress`	No	Jobs currently holding funds. Each account has a limit on jobs in progress at once.
`refill_amount_usd`	No	Amount in USD added on each auto-refill, if enabled.
`auto_refill_enabled`	Yes	Whether automatic wallet top-up is enabled.
`refill_threshold_usd`	No	Balance threshold in USD that triggers an auto-refill, if enabled.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

addedOutput schema / properties / held_usd

Added value: +{
+  "description": "Amount held for jobs still running (already taken out of balance_usd; settled to the actual cost when each job finishes, refunded if it fails).",
+  "type": "number"
+}

addedOutput schema / properties / jobs_in_progress

Added value: +{
+  "description": "Jobs currently holding funds. Each account has a limit on jobs in progress at once.",
+  "type": "number"
+}

First observedMay 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description earns credit for disclosing non-obvious behavior: submitted jobs hold estimated cost until completion, splitting the return into free (balance_usd) and reserved (held_usd) amounts.

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?

Three sentences with strict front-loading: purpose first, then when-to-call, then the one piece of non-obvious mechanics. No filler and nothing repeated from the title or schema.

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?

A zero-parameter read tool with full annotations and an output schema needs little more. The description covers purpose, timing, and the meaning of the balance-vs-held distinction, leaving no ambiguity about how or when to invoke it.

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, which sets the baseline at 4. The description spends its parameter-adjacent effort explaining the semantics of the returned balance/held fields instead, which is genuinely useful even though the output schema also exists.

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 ('Check the current prepaid wallet balance') and scopes it to the Botverse account. No sibling tool touches billing or balance, so it is trivially distinguishable from the transcode/conform/submit family.

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?

'Use before large batch jobs to confirm sufficient funds' gives an explicit triggering context and implicitly ties it to submit_workflow. It stops short of naming alternatives or stating when not to bother calling it, so it misses the 5 bar.

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

All Botverse tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?