Skip to main content
Glama

Get credit balance

get_credit_balance
Read-onlyIdempotent

Get the caller's current credit balance, monthly allocation and plan. Use this before create_video to confirm the account can afford a render (40 credits). Requires the "credits:read" scope (included by default in new keys); a key without it gets 403 INSUFFICIENT_SCOPE with a link to create a key that has it. Read-only, never charges credits. Also returns hasPaid: whether a plan charge or a credit pack purchase is on record for the account (a trial start fee alone does not count). usdPerCredit is what one credit costs this account in USD, and usdPerCreditBasis says where that number comes from.

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_credit_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: discloses the required 'credits:read' scope, the exact failure mode (403 INSUFFICIENT_SCOPE with a link to create a proper key), and confirms it never charges credits. It also flags a subtle semantic trap, that a trial start fee alone does not count toward hasPaid.

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?

Front-loads the core purpose and the create_video precondition before moving into scoping and return-field detail. Every sentence carries real information, though the trailing hasPaid/usdPerCredit clauses run long for a single-paragraph definition.

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?

With no output schema, the description carries the burden of explaining return values, and it does so for balance, plan, hasPaid and usdPerCredit/usdPerCreditBasis. Combined with auth requirements and error behavior, an agent has everything needed to call it correctly and interpret the result.

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 the baseline is 4 and there is no input semantics to add. The description instead spends its words documenting response fields (hasPaid, usdPerCredit, usdPerCreditBasis), which is useful but belongs to output semantics rather than parameter semantics.

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?

States a specific verb and resource ('Get the caller's current credit balance') and enumerates the payload: monthly allocation, plan, hasPaid, usdPerCredit. It is clearly distinct from siblings such as get_season_plan or list_pricing because it is scoped to the caller's own account.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent when to call it: 'Use this before create_video to confirm the account can afford a render (40 credits).' That names the sibling and the precondition that selects this tool, leaving little to inference.

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