Skip to main content
Glama

Get Balance

get_balance

Check your deAPI account balance and remaining credits to monitor usage before generating images, videos, audio, or other content.

Instructions

Get current account balance.

Check your deAPI account balance and remaining credits.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the burden and discloses that the value is a credit balance, which clarifies the unit. It says nothing about authentication requirements, whether the read is scoped to the calling key, or whether values refresh in real time, so an agent still has gaps for a read-only call.

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?

Two short sentences, front-loaded with the core action. The second sentence largely restates the first with the word "credits" added, which is the only piece of genuinely new information; the rest is mild redundancy.

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?

For a zero-parameter read tool whose output schema already documents the return shape, the description is nearly complete. Only auth/scoping behavior and refresh semantics are unaddressed, which are secondary given the output schema exists.

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 parameter semantics reach the baseline of 4. The description correctly implies no inputs are needed by framing it as a plain account-level read.

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?

States a specific verb and resource ("Get current account balance") and names the domain (deAPI credits). It is unambiguous against the sibling family, which are per-operation price and generation tools, though the description never explicitly says so.

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 by the second sentence ("Check your deAPI account balance and remaining credits"). There is no explicit when-to-use guidance, such as checking balance before invoking paid generation endpoints, and no stated exclusions or prerequisites.

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