Skip to main content
Glama

get_balance

Retrieves the remaining credit balance for the account associated with TURBOGEN_API_KEY, so you can check available credits before generating images, video, or audio.

Instructions

Show the remaining credit balance of the account behind TURBOGEN_API_KEY.

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
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. "Show" implies a read-only, non-destructive operation and it discloses the auth scoping (the key determines the account), which is useful. It does not state whether the call itself consumes credits, what units/currency the balance is in, or whether the value is cached or real-time — real gaps for a billing-related tool with zero annotation coverage.

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?

One sentence, front-loaded with the action and resource, with no filler or redundancy. Every clause (remaining, credit balance, account behind the key) adds information.

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?

An output schema exists, so return value structure need not be explained, and there are no parameters to document — the description is close to complete for this complexity. The only meaningful omission is the nature of the balance itself (units, whether reading is free), which would help an agent decide when to call 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, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description's only relevant framing is that account scoping comes entirely from the API key rather than from an argument, which is a small but genuinely useful clarification.

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?

"Show the remaining credit balance" names a specific verb and a specific resource, and the qualifier "of the account behind TURBOGEN_API_KEY" pins down whose balance. An agent can immediately tell this is unrelated to the generation siblings (generate_audio, generate_image, generate_video), though the description never explicitly contrasts itself with them.

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 purpose implies the usage context (checking credits, presumably before spending on generation calls), but there is no explicit statement of when to call it, when not to, or how it relates to siblings such as job_status or list_models. The agent must infer the trigger condition.

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