Skip to main content
Glama
Sign In
MCP GetBlock Server

MCP GetBlock Server

Official
by GetBlock-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get-wallet-balance

Retrieve the cryptocurrency balance for any wallet address on Ethereum or Solana by providing the address and choosing the network.

Instructions

Get the balance of a wallet address on a blockchain

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-wallet-balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe wallet address to check
chainNoBlockchain network (e.g., eth, solana)eth

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

The description only states it retrieves a balance, but does not disclose how the balance is returned (e.g., units), any required address format, or other behavioral traits. No annotations exist to supplement.

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, front-loaded sentence with no unnecessary words, earning its place.

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

Completeness2/5

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

The description lacks details on the output format (e.g., balance units) and chain values (e.g., no list beyond examples in schema). With no output schema, more context is needed for an agent to correctly interpret the result.

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%, so the schema already documents both parameters adequately. The description adds no further semantics beyond what the schema provides.

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') and resource ('balance of a wallet address on a blockchain'), distinguishing from sibling tools which cover chain info, gas price, blocks, accounts, and 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 versus alternatives, or any conditions that affect its use.

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