Skip to main content
Glama

Credit balance

balance
Read-onlyIdempotent

Returns your Wave credits: balance, held, spent today, daily cap and the last 20 ledger rows. Read-only, free. Needs sign-in (auth_challenge then auth_verify).

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": "balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
heldNo
blockNo
staleNo
ledgerNo
sourceNo
balanceNo
daily_capNo
spent_todayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "balance": {
      +      "type": "integer"
      +    },
      +    "block": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "daily_cap": {
      +      "type": "integer"
      +    },
      +    "held": {
      +      "type": "integer"
      +    },
      +    "ledger": {
      +      "type": "array"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "spent_today": {
      +      "type": "integer"
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds value beyond that by disclosing cost (free), the mandatory auth handshake sequence, and the bounded size of the ledger window (last 20 rows), which an agent otherwise could not infer.

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

Conciseness5/5

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

Two short sentences, front-loaded with the payload contents and followed by the operational constraints. Every clause carries information: fields returned, cost, auth requirement, and auth tool names.

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 with full annotations and an output schema, the description covers what an agent needs to call it successfully, including the prerequisite auth flow. It stops short of naming the companion tools an agent would use to change the daily cap or claim credits, which would have made routing fully self-contained.

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 there is nothing to disambiguate and the baseline applies. The description correctly adds no parameter commentary, focusing instead on the returned fields.

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 opens with a specific verb and resource ('Returns your Wave credits') and enumerates exactly what comes back: balance, held, spent today, daily cap, and the last 20 ledger rows. That makes the payload unambiguous, but it never distinguishes this from near-name siblings such as get_credits or theta_balance, so the agent has no stated rule for picking this one.

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?

It tells the agent how to get in ('Needs sign-in (auth_challenge then auth_verify)') and that the call is free, which is real usage context. It gives no when-to-use vs alternatives guidance and no stated exclusions against the other credit/balance tools in the catalog.

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