Skip to main content
Glama
Sign In

VerifyLite

by io.github.SecondShotAI
OverviewDiscussionsAdmin

Base wallet balance: ETH, USDC and any ERC-20 tokens, transaction count, wallet or contract

chain_balance
Read-only

Base mainnet balance for one address: ETH and USDC (human-readable and raw), plus up to 10 ERC-20 tokens you list (with symbol and decimals), transaction count, and whether it is a wallet or a contract. One price for 0 to 10 tokens. Useful for checking a wallet is funded before a payment, confirming a payout or airdrop landed, tracking agent or treasury wallets, or screening a counterparty. Read-only. Not charged for invalid addresses or when Base can't be reached. Paid via x402; see list_prices.

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

Input Schema

NameRequiredDescriptionDefault
tokensNoOptional: up to 10 ERC-20 token contract addresses on Base to also return balances for (an array, or one comma-separated string). ETH and USDC are always included.
addressYes0x address on Base (40 hex characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tokens / items / anyOf
      Previous value: -[
-  {
-    "maxLength": 512,
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "items": {
-      "anyOf": [
-        {
-          "maxLength": 512,
-          "type": "string"
-        },
-        {
-          "type": "number"
-        },
-        {
-          "type": "boolean"
-        }
-      ]
-    },
-    "maxItems": 200,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "maxLength": 512,
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "items": {
+      "anyOf": [
+        {
+          "maxLength": 512,
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "boolean"
+        }
+      ]
+    },
+    "maxItems": 200,
+    "type": "array"
+  },
+  {
+    "additionalProperties": {},
+    "type": "object"
+  }
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / tokens / items / anyOf
      Previous value: -[
-  {
-    "maxLength": 512,
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  }
-]New value: +[
+  {
+    "maxLength": 512,
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "items": {
+      "anyOf": [
+        {
+          "maxLength": 512,
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "boolean"
+        }
+      ]
+    },
+    "maxItems": 200,
+    "type": "array"
+  }
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / tokens
      Added value: +{
+  "description": "Optional: up to 10 ERC-20 token contract addresses on Base to also return balances for (an array, or one comma-separated string). ETH and USDC are always included.",
+  "items": {
+    "anyOf": [
+      {
+        "maxLength": 512,
+        "type": "string"
+      },
+      {
+        "type": "number"
+      },
+      {
+        "type": "boolean"
+      }
+    ]
+  },
+  "maxItems": 1000,
+  "type": "array"
+}
  4. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, it discloses the billing model (one price for 0 to 10 tokens), the failure-charging policy (not billed for invalid addresses or unreachable Base), and the payment mechanism (x402, pointing to list_prices). Those are operationally important details the annotations cannot express.

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 payload is front-loaded: what is returned, then pricing, then use cases, then billing caveats. Every sentence carries distinct information with no filler or repetition.

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

Completeness5/5

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

With no output schema, the description still describes the return shape (human-readable and raw values, symbol and decimals per token, tx count, wallet/contract flag) and covers cost, failure, and payment mechanics. An agent can decide and call it correctly without further information.

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 both parameters are already documented, and the description largely restates the token cap and that ETH/USDC are always included. It adds the pricing rationale for 0-10 tokens but nothing about address format or how the comma-separated string form behaves beyond what the schema says.

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?

It names a precise resource (Base mainnet balance for one address) and enumerates the returned data: ETH, USDC, up to 10 listed ERC-20s, transaction count, and wallet-vs-contract classification. That specificity separates it from siblings like chain_token, token_holders, and wallet_transfers at a glance.

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?

It provides four concrete scenarios (checking funding before a payment, confirming a payout or airdrop, tracking treasury/agent wallets, screening a counterparty), so the agent knows when this is the right call. It doesn't explicitly name which sibling to use instead when, for example, only token holders or transfer history are needed, so no exclusions are stated.

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

All VerifyLite toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources