AI3D Studio

Check credit balance

get_balance

Read-onlyIdempotent

Get the credits this account can spend now (and how many of them come from the subscription or are permanent), the plan name when there is one, and — when you are connected with an API key that has a monthly credit limit — that limit, what the key has used this month, and when it resets. Read-only.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`plan`	Yes	The active subscription plan; null on pay-as-you-go.
`account`	Yes
`credits`	Yes
`api_key_limit`	Yes	Only for an API key with a monthly credit limit.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 24, 2026
- removedOutput schema / properties / credits / properties / permanent_expires_at / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / credits / properties / permanent_expires_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / credits / properties / subscription_expires_at / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / credits / properties / subscription_expires_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / plan / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / plan / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedOct 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description's closing 'Read-only' merely restates that. The only added behavioral nuance is that the monthly-limit fields appear conditionally when connected via a rate-limited API key, which is helpful but largely a return-value detail the output schema already covers.

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?

A single front-loaded sentence leads with the primary value (spendable credits) before the optional details. It is dense with parenthetical asides but every clause describes a real returned field, so little is wasted.

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 parameters, a full output schema, and complete annotations, the description needs only to frame what the call answers, which it does, including the conditional API-key branch. Slightly more guidance on when an agent should reach for it would make it fully sufficient.

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 is nothing for the description to disambiguate; the baseline of 4 applies. It correctly signals a no-argument call by not introducing any input concepts.

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 uses a specific verb ('Get') and a well-defined resource (spendable credits, their subscription/permanent split, plan name, and API-key monthly limit with usage and reset). This clearly separates it from cost-forecasting siblings like estimate_cost, though no sibling is named explicitly.

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 only implied: an agent can infer this is a pre-flight check for available credits, but the description never says when to call it versus estimate_cost or what happens if the balance is zero. No exclusions or alternatives are stated.

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

All AI3D Studio 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?