Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

erc20-balance

[x402 paid: $0.010 USDC on Base] ERC-20 token balance for any Base wallet, decimals applied, human readable. tools/call returns the live payment challenge.

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": "erc20-balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoexample: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
addressNoexample: 0x75F93F8aD9A437D415F277dEF4Cc268a8Bf1C45C

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does disclose non-obvious behavior: a $0.010 USDC on Base x402 charge and the fact that tools/call returns a live payment challenge. It also characterizes the response as human-readable with decimals applied. It omits failure modes (invalid address, unsupported chain) and any rate-limit or retry behavior.

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?

Three compact clauses with the paid-access notice front-loaded, then resource, then payment-flow behavior. No filler and nothing buried.

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 two-parameter read tool with no output schema, the description covers the payment prerequisite, the chain scope, and the return shape well enough to invoke it. Minor gaps remain around error and edge-case handling, which is acceptable at this complexity.

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 description coverage is 100%, so the schema already documents both properties, albeit only as bare address examples. The description frames the pair as token + wallet implicitly ('ERC-20 token balance for any Base wallet') but adds no format, required-ness, or default semantics beyond the schema.

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+resource: ERC-20 token balance for any Base wallet, with the output shape (decimals applied, human readable) called out. It is distinguishable from sol-balance by the ERC-20/Base scoping, though it never names that sibling explicitly.

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?

Use is implied by the resource and chain scope ('any Base wallet'), so an agent can infer this is the ERC-20-on-Base read path. There is no explicit when-to-use/when-not guidance and no named alternative for non-Base or native-asset balances.

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