Skip to main content
Glama

Get ClawCall plan and balance

get_balance
Read-only

Read the signed-in user's current plan, leftover prepaid balance, or trial allowance. Use after a quota/plan error or when the user asks what they have left. Explain allowance limits neutrally and preserve returned informational, sign-in, or support links.

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
planYes
trialYes
legacyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnly=true, destructive=false, openWorld=false, so safety is covered. The description adds behavior the annotations cannot: it warns that allowance limits should be explained neutrally and that informational, sign-in, or support links in the response must be preserved — useful output-handling context. It stops short of saying how a signed-out or unauthenticated state is reported, which is the one remaining gap.

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?

Three short sentences, front-loaded with purpose followed by usage triggers, with zero preamble. The final sentence bundles two separate output instructions (neutral framing plus link preservation) and is slightly compressed rather than cleanly split, which is the only reason it is not a 5.

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 input parameters, an output schema already documenting the return shape, and full annotation coverage, the description only needs to supply purpose, triggers, and output-handling rules — and it does all three. An agent has everything required to call this correctly and to present the result appropriately.

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 no parameter meaning to add and the baseline of 4 applies. The description correctly spends no words restating the empty schema.

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 opens with a specific verb ('Read') and names three precise resources: current plan, leftover prepaid balance, and trial allowance. None of the sibling tools (place_call, get_call, hangup_call, etc.) deal with billing/plan state, so an agent can rule this in or out without opening the schema.

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

Usage Guidelines4/5

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

It gives two explicit triggers — after a quota/plan error, or when the user asks what they have left — which is exactly the condition an agent needs. No exclusions or named alternatives are offered, but the sibling catalog contains no overlapping tool, so the absence costs little.

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.