AnyAPI

Check wallet balance

get_balance

Read-only

Get the remaining wallet balance (in USD) for the AnyAPI key supplied as a Bearer token. Requires a valid AnyAPI key.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`context`	Yes	Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."

Output Schema

TableJSON Schema

Name	Required	Description	Default
`balanceUsd`	Yes	remaining wallet balance for this API key, in USD

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 3, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties

Added value: +{
+  "context": {
+    "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+    "type": "string"
+  }
+}

addedInput schema / required
```
Added value: +[
+  "context"
+]
```

First observedJun 18, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already mark the tool as read-only and non-destructive. The description adds useful behavioral context: the balance is tied to a specific Bearer-token key, and a valid key is required, indicating an auth-dependent lookup. This goes beyond the structured hints and does not contradict them.

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 a single sentence that states the action, resource, unit, and auth requirement with no filler. Information is front-loaded and every word earns its place.

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?

This is a simple read-only balance lookup. Combined with the readOnly and destructive annotations, an output schema, and a fully documented parameter schema, the description covers the goal, auth mechanism, and prerequisite. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter, 'context', is fully documented in the schema with word-count, perspective, and content constraints, so schema coverage is 100%. The description does not attempt to re-explain the parameter, and the baseline of 3 is appropriate since the description adds no parameter-level semantics beyond what the schema already provides.

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 uses a specific verb ('Get'), identifies the resource ('remaining wallet balance in USD'), and states the auth mechanism ('AnyAPI key supplied as a Bearer token'). This clearly distinguishes it from siblings like list_apis, get_api, or quote_api, so an agent can select it unambiguously for balance queries.

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 description implies when to use the tool (whenever the remaining wallet balance is needed) and states the prerequisite of a valid AnyAPI key. However, it does not explicitly mention alternatives or when not to use it, leaving sibling differentiation to the agent's inference.

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

All AnyAPI 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.