Skip to main content
Glama

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.

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
planYesThe active subscription plan; null on pay-as-you-go.
accountYes
creditsYes
api_key_limitYesOnly for an API key with a monthly credit limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed6 schema fields changed
    • 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"
      +]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the 'Read-only' sentence in the description merely restates structured data and earns no credit. The description does add real behavioral context by disclosing that the response shape varies with authentication context (API key with a monthly limit yields limit/usage/reset fields, otherwise it may not), which is the kind of conditional behavior an agent cannot learn from the annotations.

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?

The definition is a single front-loaded sentence that leads with the primary resource and then enumerates the additional fields. The em-dash aside about API-key limits is somewhat dense and the trailing 'Read-only' is redundant with annotations, but overall it is compact and free of filler.

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?

For a zero-parameter, read-only tool with a full output schema and complete annotation coverage, this description supplies everything the agent needs: what is fetched, which fields are conditional, and the auth-dependent variability. There is no output schema gap to fill and no parameter ambiguity to resolve.

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 (0 params), so the baseline of 4 applies. The description correctly spends no words on parameter syntax and instead describes what varies in the response, which is the right allocation for a zero-argument tool.

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 names a specific verb and resource ('Get the credits this account can spend now') and enumerates the components returned: subscription vs. permanent credits, plan name, and API-key monthly limit with usage and reset time. This is far more precise than the title alone and lets an agent distinguish it from cost-estimation siblings like estimate_cost, which computes costs rather than reporting current balances.

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: it explains that certain fields appear 'when you are connected with an API key that has a monthly credit limit', which tells the agent what triggers extra output but not when to call this versus alternatives such as estimate_cost. No explicit when-to-use or when-not-to-use guidance is given, so the agent must infer that this tool is for checking current balance rather than projecting spend.

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