Skip to main content
Glama
Sign In
Crypto MCP Server

Crypto MCP Server

by rex-automata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_eth_balance

Get the current Ethereum balance for any wallet address. Simply provide the address to check its ETH holdings.

Instructions

Get Ethereum wallet balance for a given address

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
addressYesEthereum wallet address (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are present, and the description does not disclose any behavioral traits such as idempotency, rate limits, or data freshness. The bare statement 'Get...balance' leaves the agent guessing about side effects or restrictions.

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?

The description is a single, concise sentence with no unnecessary words. It is front-loaded with the action and resource, making it easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one required parameter and no output schema, the description covers the basic purpose. However, it omits details like the denomination (wei/ether) and response format, which could be helpful but are not essential.

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% (the only parameter 'address' is described in the schema as 'Ethereum wallet address (0x...)'). The description adds no further semantic value beyond rephrasing the schema. Baseline is 3.

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 clearly states the action ('Get'), the resource ('Ethereum wallet balance'), and the input condition ('for a given address'). It unambiguously distinguishes this tool from siblings like 'get_btc_balance' or 'get_eth_transactions'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool vs alternatives, nor any conditions or prerequisites. For a simple read tool, this omission is noticeable but not critical.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools