Skip to main content
Glama

Credit balance

get_credit_balance
Read-onlyIdempotent

Your plan and credit balance (plan credits and purchased credits), whether your plan includes scheduling and the autopilot, and, for an app allowed to spend, its daily credit limit and what it has left today (UTC).

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

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, idempotent behavior, so the description's job is to add return-side context — which it does well. It discloses that the app-specific daily limit and remaining-today figures are conditional ('for an app allowed to spend') and that the window is UTC, both of which are non-obvious behavioral facts. It stops short of saying what is returned when the plan has no credits or when the caller is unauthenticated.

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?

A single sentence with no filler, and the primary payload (plan and credit balance) is front-loaded before the secondary entitlements and the app-specific limit. It is dense and slightly run-on due to the nested parenthetical and commas, but every clause carries distinct 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?

With no output schema, the description carries the burden of explaining return values, and it enumerates the returned fields including the conditional app-limit block and its UTC boundary. Given a zero-parameter read-only getter, that is nearly complete; only edge-case behavior (no plan, no app context, error conditions) is unaddressed.

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 empty schema is fully described, so there is no parameter semantics to elaborate. The description correctly spends none of its budget restating inputs and instead describes the implied context (which app's limit is reported).

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?

The description names a specific resource and enumerates exactly what is returned: plan credits, purchased credits, whether scheduling/autopilot are included, and per-app daily credit limit with remaining amount. It is clearly distinct from siblings like estimate_cost or list_* tools, though it never uses an explicit verb such as 'returns' and is phrased as a noun list rather than a statement of action.

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 nature of the tool (checking balance/plan entitlements). There is no explicit 'use this when...' guidance, no mention of estimate_cost as the alternative for predicting spend, and no statement about when this tool is not appropriate. A reader can infer the use case, but nothing is spelled out.

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