Skip to main content
Glama

Get Credit Balance

get_credit_balance
Read-onlyIdempotent

[Meta · free] Return the authenticated user's current credit balance, the current calendar month's credit period (UTC), that month's allocation if one was granted (null otherwise), credits used since the period started, and the most recent allocation. 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_credit_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add genuine behavioral detail beyond them — the period is a UTC calendar month, allocation may be null when none was granted, and usage is measured from the period start. That is useful but limited to return semantics; nothing is said about auth requirements, rate limits, or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is one front-loaded sentence with no filler and every listed field is informative. However, the "free" claim is stated twice ("[Meta · free]" and a trailing "Free."), which is avoidable duplication in an otherwise tight definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 enumerate the fields including the null case. It stops short of covering error conditions, currency/unit framing, or how the reported values relate to the usage-history tool, which leaves gaps for a no-argument tool agents will call alongside others.

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 and the schema is an empty object, so there is no parameter meaning to convey — baseline 4 applies. The description correctly spends no words on inputs.

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?

Uses a specific verb ("Return") plus a precisely enumerated resource: balance, current calendar-month credit period (UTC), allocation or null, credits used since period start, and most recent allocation. It is clearly a read of credit data, but it never distinguishes itself from plausible siblings like get_usage_history or get_cost_estimate, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus get_usage_history, get_cost_estimate, or get_alerts — the adjacent credit/usage tools. The "[Meta · free] / Free." framing hints that the call costs nothing, but that is a pricing note, not usage guidance, and 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