ChainHilt

wallet_balance

Reads native or ERC-20 token balances for a local or specified wallet address on a supported chain, defaulting to the active chain when no chain ID or token address is given.

Instructions

Read the local/passed MCP wallet native or ERC-20 balance on a chain. If no address is passed, reads local MCP wallet address. If no tokenAddress is passed, reads native balance. If no chainId is passed, reads the active chain; mcp_status lists the chains.

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

Input Schema

Name	Required	Description	Default
`address`	No
`chainId`	No
`tokenAddress`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral load: it does signal a read-only operation and explains how omitted arguments are resolved. It says nothing about error handling for invalid or unknown addresses, whether balances are returned raw or decimal-adjusted, or permission/auth requirements.

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?

One lead sentence stating purpose followed by three terse conditional lines covering each parameter's default. Every line earns its place and the core capability is front-loaded.

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?

For a read-only balance lookup with three optional parameters and no output schema, the description covers the resolution of every input default. The main remaining gap is what the returned balance looks like (units/decimals), which an agent might need to interpret the result.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does for all three parameters: address defaults to the local MCP wallet, tokenAddress distinguishes ERC-20 from native, and chainId defaults to the active chain. Format details (0x pattern, integer bounds) are left to the schema, which is acceptable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read ... wallet native or ERC-20 balance on a chain') and distinguishes the two balance types. It does not explicitly contrast with sibling wallet tools like wallet_setup, but the operation is unambiguous on its own.

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 explicit defaulting rules for all three optional parameters (local MCP wallet address, native balance, active chain), which tells the agent exactly how to invoke it with zero, one, or several arguments. It also points to mcp_status for discovering chains, though it offers no when-not-to-use guidance.

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

Deploy Server