Skip to main content
Glama

Get balance

get_balance
Read-onlyIdempotent

Your agent account: CREDIT balance, spent today, daily cap, per-call maximum, free answers left and the deposit address. Free; needs an API key.

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
idYes
api_keyYes
balanceYes
daily_capYes
spent_todayYes
owner_addressYes
deposit_addressYes
free_ask_calls_leftYes
per_call_max_defaultYes
deposits_auto_creditedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior context: the call is free and it requires an API key for authentication. It does not mention rate limits or caching, but for a zero-parameter read those are minor.

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?

A single dense sentence front-loads the account context, then lists the returned fields, closing with the two operational facts (cost and auth). Every clause carries information and nothing is repeated from the annotations.

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?

The tool is trivial to invoke (no parameters) and an output schema exists, so return-value detail is a bonus rather than a requirement. With cost, authentication, and payload all covered, 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 schema has no parameters, so there is nothing for the description to disambiguate; baseline for a zero-parameter tool applies. The description correctly spends its words on the return payload instead of inventing parameter guidance.

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 ('Your agent account') and enumerates exactly what is returned: CREDIT balance, spent today, daily cap, per-call maximum, free answers left, deposit address. An agent knows precisely what it gets. It stops short of naming a sibling (e.g. ask, call_endpoint) as the alternative for paid usage, so it is clear but not sibling-differentiated.

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?

'Free; needs an API key' establishes a prerequisite and the cost of calling, which implies checking status before spending credits. However, there is no explicit when-to-use statement, no exclusion, and no named alternative such as quote_credit_purchase for topping up once the balance is low. Usage is inferable rather than stated.

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