Skip to main content
Glama

BRAINIAC Wallet Intelligence

Analyze wallet

wallet-intelligence_analyze
Read-onlyIdempotent

Consolidate wallet balances and observed transfer activity on Base Mainnet with block range coverage information. Price $0.10 USDC. POST /api/v1/wallet-intelligence/analyze. 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_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
snapshotNosnapshot. Object.
transfersNotransfers. Array.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
walletAddressNowalletAddress. String.
transferSummaryNotransferSummary. Object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the $0.10 USDC price, the x402 payment handshake, and the fact that an unpaid call returns payment terms without executing — critical for an agent to avoid mistaking a 402 response for a failure. It stops short of describing what 'block range coverage information' looks like in the result.

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?

Three short sentences with the purpose front-loaded, followed by cost and payment behavior. The bare endpoint string 'POST /api/v1/wallet-intelligence/analyze' is the least valuable element and could be dropped, but overall there is little waste.

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?

The tool is a read-only aggregate with a full output schema and rich annotations, so the description needn't explain return values. It covers chain, cost, and payment failure mode, which is what an agent needs before calling. The remaining gap is the absence of routing guidance relative to snapshot/transfers, which matters given the crowded sibling set.

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 walletAddress, fromBlock, toBlock, and tokenAddresses are already documented in the schema. The description's phrase 'with block range coverage information' hints at the role of fromBlock/toBlock but adds no format or default detail, and it never mentions tokenAddresses filtering. Baseline 3 applies when the schema does the heavy lifting.

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?

The description states a specific verb and resource: 'Consolidate wallet balances and observed transfer activity on Base Mainnet,' which is far more informative than the title 'Analyze wallet.' It does not, however, differentiate itself from close siblings such as wallet-intelligence_snapshot or wallet-intelligence_transfers, leaving the agent to infer which one returns balances versus raw transfers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no reference to alternatives among the six sibling tools. The only conditional instruction is about payment ('An unpaid call returns the x402 payment terms and does not run'), which is a prerequisite, not usage guidance.

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