Skip to main content
Glama

get_balance

Get token balances for the authenticated wallet across one or all networks. Returns cached balance data. Requires authentication.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It usefully reveals two behavioral traits the agent could not otherwise know — authentication is required, and the returned data is cached (i.e., potentially stale) — but says nothing about supported networks, failure modes, or how caching affects freshness.

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?

Three short, front-loaded sentences: what it returns, an important data-freshness caveat, and the auth prerequisite. Nothing is wasted and the most decision-relevant facts come first.

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 tool with no output schema, the description covers the essentials: scope (authenticated wallet), coverage (one or all networks), freshness (cached), and the auth requirement. Only the set of supported networks and how to obtain non-cached data remain unstated.

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?

There are zero input parameters, so the schema sets a baseline of 4. The phrase 'across one or all networks' hints at a network selector that the empty schema does not actually expose, which is a minor ambiguity rather than a documentation gain.

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 gives a specific verb and resource ('Get token balances') plus a clear scope ('authenticated wallet across one or all networks'), so an agent knows exactly what it retrieves. It does not, however, distinguish this from adjacent portfolio-style siblings such as get_positions or get_trading_overview.

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: the mention of 'one or all networks' and 'authenticated wallet' suggests when the tool applies, and 'Requires authentication' is a prerequisite, but there is no explicit statement of when to prefer this over get_positions or get_trading_overview, and no exclusions.

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