Skip to main content
Glama

Claim a TFUEL deposit

balance_claim

Claims TFUEL you sent to the deposit_info address as Wave credits. Each tx is verified on Theta and claimed once. Returns credits added and your balance. Free. Needs sign-in (auth_challenge then auth_verify). Already claimed, wrong recipient or unconfirmed: an error code, nothing added.

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_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
tx_hashNoTheta tx hash, 0x + 64 hex
tx_hashesNoOr up to 10 Theta tx hashes claimed together
accept_termsNotrue on your first claim to accept the prepaid terms in deposit_info

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / accept_terms / default
      Added value: +false
    • addedInput schema / properties / accept_terms / description
      Added value: +"true on your first claim to accept the prepaid terms in deposit_info"
    • addedInput schema / properties / tx_hash / description
      Added value: +"Theta tx hash, 0x + 64 hex"
    • addedInput schema / properties / tx_hash / pattern
      Added value: +"^0x[0-9a-fA-F]{64}$"
    • addedInput schema / properties / tx_hashes / description
      Added value: +"Or up to 10 Theta tx hashes claimed together"
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: on-chain verification, single-claim-per-tx semantics, the return payload ('credits added and your balance'), that the call is free, and the exact failure envelope (already claimed / wrong recipient / unconfirmed → error code, nothing added). This is consistent with idempotentHint=false and destructiveHint=false. Annotation Contradiction is not present.

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?

Front-loads the core action and keeps every sentence informational, including the failure modes. The staccato fragments ('Free. Needs sign-in...') are efficient but slightly telegraphic, making the auth requirement easy to skim past.

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?

With no output schema, the description usefully summarizes the return value and error behavior, and it covers the auth prerequisite. The gap is that required parameters list is empty yet one of tx_hash/tx_hashes must practically be supplied, and accept_terms' first-claim requirement is left to the schema.

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?

Schema description coverage is 100%, so tx_hash, tx_hashes and accept_terms are already documented in the schema. The description adds no format or selection guidance for choosing singular vs. batch, nor any note that accept_terms is required on first use, so the baseline of 3 applies.

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?

States a specific verb and resource ('Claims TFUEL you sent to the deposit_info address as Wave credits'), which pins down both the object and the direction of the operation. It also implicitly distinguishes itself from the sibling deposit_info (which supplies the address) and from balance (which only reads).

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?

Gives a concrete precondition and ordering ('Needs sign-in (auth_challenge then auth_verify)'), routing the agent to the correct siblings before calling. It lacks an explicit 'do not use when' clause or a direct comparison to deposit_info beyond the implicit sequencing.

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