Skip to main content
Glama

Wallet balances and activity (Base)

kairos_wallet_activity
Read-onlyIdempotent

Wallet balances and activity on Base: EOA, EIP-7702 delegated EOA or contract, ETH balance, nonce, proxy implementation (EIP-1967, legacy OpenZeppelin, EIP-1822, EIP-1167), balances of 10 major Base tokens and USDC/WETH transfers in and out over the last 24 h (counts, amounts, latest transfer; marked partial if part of the scan failed). On-chain data only. Optional chain: base (default) or base-sepolia. Read-only. Free for MCP clients up to 3 reports per client per day; beyond the quota the response lists the paid access options (x402 on the HTTP route, or a prepaid credit key) instead of a report. Never pays or signs anything itself. AI-generated data and analysis; not financial advice.

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

Input Schema

NameRequiredDescriptionDefault
chainNoChain to read; defaults to base
addressYesWallet or contract address
credit_keyNoOptional prepaid credit key for use beyond the free daily quota.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnly/destructive/idempotent annotations, it discloses the quota mechanism (3 free reports per client per day), what happens when the quota is exceeded (the response lists x402 or prepaid credit-key paid options instead of a report), and the guarantee that the tool never pays or signs. It also flags a real output subtlety: transfers are marked partial if part of the scan failed. That is exactly the kind of behavior an agent cannot infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the resource and scope, then moves through data returned, chain option, pricing/quota, and disclaimers in a logical order. The single dense paragraph is long but nearly every clause carries information; the "AI-generated data and analysis; not financial advice" tail is the only weakly load-bearing sentence.

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?

There is no output schema, so the description must convey return content, and it does: balances, nonce, proxy implementation type, transfer counts/amounts/latest, plus the partial-result caveat and the quota-exceeded response shape. For a read-only, single-address tool with three documented parameters, an agent has everything needed to call and interpret it.

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 all three parameters, including the chain default and the credit_key meaning. The description restates the chain default and ties credit_key to the paid-access path, but adds no syntax, constraints or format detail beyond what the schema states. Baseline 3 is appropriate.

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 leads with a specific verb+resource ("Wallet balances and activity on Base") and then enumerates the exact data returned: account type (EOA, EIP-7702 delegated, contract), ETH balance, nonce, proxy implementation standards, top-10 token balances and USDC/WETH transfer counts/amounts over 24h. Nothing overlaps with the unrelated siblings kairos_catalog or kairos_page_markdown, so the tool is unambiguously identifiable.

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 establishes clear usage context: on-chain data only, read-only, optional chain of base or base-sepolia, and the free-tier limit of 3 reports per client per day. It does not name an alternative tool or state an explicit when-not condition, but the sibling tools cover entirely different domains, so the residual risk of mis-selection is low.

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