Skip to main content
Glama

Theta balance

theta_balance
Read-onlyIdempotent

Returns the THETA and TFUEL balances of a Theta mainnet address, in whole tokens (theta, tfuel as numbers), plus exact wei amounts as strings (thetawei, tfuelwei). Read-only, free, no key; counts as 2 calls. Bad address: error bad_args.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "theta_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesTheta wallet address, 0x + 40 hex, e.g. 0xcb20457aeb7ad30dbae281efbfd7c48137db1894

Output Schema

NameRequiredDescriptionDefault
blockNo
staleNo
tfuelNo
thetaNo
sourceNo
addressNo
tfuelweiNo
thetaweiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Theta wallet address, 0x + 40 hex, e.g. 0xcb20457aeb7ad30dbae281efbfd7c48137db1894"
    • addedInput schema / properties / address / pattern
      Added value: +"^0x[0-9a-fA-F]{40}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "address": {
      +      "type": "string"
      +    },
      +    "block": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    },
      +    "tfuel": {
      +      "type": "number"
      +    },
      +    "tfuelwei": {
      +      "type": "string"
      +    },
      +    "theta": {
      +      "type": "number"
      +    },
      +    "thetawei": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. Beyond them, the description adds useful behavior: a cost of 2 calls, no key requirement, and an error contract ('Bad address: error bad_args'). It does not mention rate limits or caching, but for a read-only lookup it goes clearly beyond the annotation baseline.

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 dense sentences, no filler. The return shape comes first, so the most important information is front-loaded, and the pricing and error details follow. Every clause carries information: units, cost, key requirement, and error code.

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?

The definition covers the return units, cost, access requirement, error case, and chain scope. With an output schema present, the description does not need to detail the response fields, and it does not waste space repeating them. The only real gaps are rate-limit behavior and whether testnet addresses are rejected.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With one parameter and 100% schema description coverage, the baseline is already 3, because the schema fully documents the address format, regex, and a valid example. The description adds only the 'mainnet' qualifier, which the schema does not state, so the net gain is small but non-zero.

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 concrete verb and resource: 'Returns the THETA and TFUEL balances of a Theta mainnet address.' It further pins down scope (mainnet only, both tokens, whole-token plus wei units), which is enough to separate it from generic siblings like balance, balance_claim, price_list, and tfuel_swap.

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 the call is 'Read-only, free, no key' and that it 'counts as 2 calls,' which is real cost guidance relevant to choosing it. But it never says when to prefer this over the other balance or swap tools, or of any exclusion. Usage is implied 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