Skip to main content
Glama

Credit balance

get_balance
Read-only

Your credits: the total, the part image and video generation can use (the welcome credits can't), each lot with its expiry, the plan, auto top-up, the daily generation cap and storage used of the plan's allowance. For the studio's owner, owner is true: nothing is ever charged, so a balance of 0 stops nothing. Free.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely non-obvious behavior beyond that: welcome credits cannot be used for image/video generation, each lot carries its own expiry, and owner accounts are never charged so a zero balance does not block them. It omits refresh cadence and error behavior, which keeps it from a 5.

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?

It is a single dense sentence with the most important item ('the total') first, followed by the qualifying details. Every listed field earns its place, though the long run-on structure and the parenthetical caveat make it slightly harder to scan than it could be.

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 output schema, the description carries the burden of explaining what comes back, and it does so field by field. For a zero-parameter read tool with readOnlyHint, that is nearly complete; only the freshness of the numbers and any failure modes are unstated.

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 no parameters, so the baseline is 4. Nothing in the description misrepresents the call signature, and no parameter meaning is needed.

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 enumerates exactly what get_balance reports: total credits, generation-usable credits, expiry per lot, plan, auto top-up, daily cap and storage. That is far more specific than the name alone and clearly distinguishes it from cost-estimation siblings like estimate_cost. It loses a point only because it reads as a content list without an explicit verb such as 'reports' or 'returns'.

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 rather than stated: the mention that a balance of 0 stops nothing for owners implies this is a pre-generation check, but the description never says when to call it instead of estimate_cost or before generate_assets. No exclusions or prerequisites are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources