Skip to main content
Glama
Sign In
broke2built-skills-mcp

broke2built-skills-mcp

by lordbasilaiassistant-sudo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

multichain_balance

Retrieve native balance for a single address across 5 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon) in one API call.

Instructions

Native balance for one address across 5 EVM chains in one call. (free taste tier: 20 calls/day/IP — set ALLY_KEY env for 100/day free)

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

Input Schema

NameRequiredDescriptionDefault
chainNoeth|base|arbitrum|optimism|polygon (or "all" for gas-tracker)
addressYesThe address to analyze

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.1/5.0
Behavior4/5

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

In the absence of annotations, the description discloses key behavioral traits: rate limits, environment variable for quota increase, and the gas-tracker concept for 'all' chain. It does not detail error handling or response format, but for a read-only balance check this is adequate.

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 efficient sentences: first encapsulates the core function, second adds essential usage limits. No redundant or verbose phrasing. Every word serves a purpose.

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 simple tool with no output schema, the description should clarify expected return format (e.g., map of chain→balance). It only mentions 'Native balance', leaving the agent to guess the structure. Also missing error cases or prerequisites beyond the key.

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 baseline is 3. The description adds minimal value beyond the schema: it contextualizes 'all' as gas-tracker but does not elaborate on input format or constraints. It repeats schema info without significant enrichment.

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 tool's purpose: retrieving native balance for one address across 5 EVM chains in a single call. It lists specific chains and mentions the 'all' option for gas-tracker, distinguishing it clearly from unrelated sibling tools.

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?

The description provides usage limits (20 calls/day/IP, upgradeable via ALLY_KEY) which guides the agent on rate constraints. It does not explicitly mention when to use versus alternatives, but sibling tools are unrelated, so no confusion arises.

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