Skip to main content
Glama

BRAINIAC Wallet Intelligence

Get wallet transfers

wallet-intelligence_transfers
Read-onlyIdempotent

Retrieve ERC-20 transfer activity within a requested block range on Base Mainnet using public JSON-RPC. Price $0.05 USDC. POST /api/v1/wallet-intelligence/transfers. An unpaid call returns the x402 payment terms and does not run.

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": {
      "walletAddress": "<walletAddress>"
    },
    "name": "wallet-intelligence_transfers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit, integer, from 1 to 1000. Required.
toBlockNotoBlock, integer, from 0 to 9007199254740991. Optional.
fromBlockNofromBlock, integer, from 0 to 9007199254740991. Optional.
walletAddressYeswalletAddress, string. Required.
tokenAddressesNotokenAddresses, array. Optional.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
toBlockNotoBlock. Number.
incomingNoincoming. Object.
netFlowsNonetFlows. Array.
outgoingNooutgoing. Object.
fromBlockNofromBlock. Number.
transfersNotransfers. Array.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
currentBlockNocurrentBlock. Number.
transferCountNotransferCount. Number.
walletAddressNowalletAddress. String.
scannedBlockRangeNoscannedBlockRange. String.
uniqueCounterpartiesNouniqueCounterparties. Array.
uniqueTokenContractsNouniqueTokenContracts. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the description isn't needed for the safety profile. It still adds real behavioral context the annotations cannot: a $0.05 USDC price, the POST endpoint, the public JSON-RPC data source, and critically that an unpaid x402 call returns payment terms and does not execute. Pagination and rate-limit behavior remain undisclosed.

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?

Four short sentences, front-loaded with the core purpose followed by the cost, endpoint, and payment failure mode — every sentence carries distinct information. It is slightly telegraphic and the endpoint string adds little for an agent that never constructs URLs directly, but there is no padding.

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?

An output schema exists, so return-value explanation is correctly omitted, and the description covers the non-obvious risks (cost, x402 gating). The main remaining gap is behavior of the limit/paging interaction and any defaults for the block range when fromBlock or toBlock is omitted, which the description leaves unstated.

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 all five parameters are already documented structurally; the baseline of 3 applies. The description only loosely restates the block-range concept already captured by fromBlock/toBlock and says nothing about how limit interacts with the result set or what tokenAddresses filtering means in practice.

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 ('Retrieve ERC-20 transfer activity'), plus the chain (Base Mainnet) and scoping (requested block range). This is concrete enough to distinguish it from a general transaction lookup, but it does not explicitly name a sibling (e.g., wallet-intelligence_transaction) to draw the boundary.

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?

The block-range framing implies when this tool fits (historical ERC-20 transfer lookups), and the payment note signals a prerequisite. However, there is no explicit when-to-use vs. when-not guidance and no statement of which sibling to pick for native transfers, approvals, or aggregate analysis — the agent must infer that.

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