Skip to main content
Glama

get_eth_balance

Get ETH balance for a Base mainnet address. Returns balance_wei (string) and balance_eth (formatted).

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": "get_eth_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes0x-prefixed 40-char hex address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the return shape (balance_wei and balance_eth), which usefully clarifies units, and the operation is implicitly a read, but there is no statement about auth requirements, rate limits, error behavior for malformed or non-existent addresses, or what a zero/uninitialized account returns.

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 short sentences, front-loaded with purpose and scope, followed immediately by the return values. Nothing is redundant or padded.

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?

This is a simple single-parameter read tool with full schema coverage, and the description compensates for the missing output schema by naming both returned fields. An agent has everything needed to call it correctly and interpret the response.

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 coverage is 100% and the single parameter is fully documented as a '0x-prefixed 40-char hex address'. The description adds only that the address is on Base mainnet; it adds no format or validation detail beyond the schema, 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 ('Get ETH balance') plus the exact network scope ('Base mainnet address'), which is what separates it from a generic or multi-chain balance lookup. It also names the two return fields, so an agent knows precisely what comes back without opening a schema.

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?

The chain scope ('Base mainnet') implicitly tells the agent when this tool applies versus an L1 or other-network balance check, but there is no explicit statement of when to use this over alternatives such as get_token_balance, and no mention of error or unsupported-address cases.

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