Skip to main content
Glama

BRAINIAC Wallet Intelligence

Get wallet snapshot

wallet-intelligence_snapshot
Read-onlyIdempotent

Retrieve current wallet balance and supplied token balances on Base Mainnet with USD valuations from DeFiLlama. Token approvals/allowances are not included; use security/approvals before moving funds. Price $0.02 USDC. POST /api/v1/wallet-intelligence/snapshot. 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_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletAddressYeswalletAddress, string. Required.
tokenAddressesNotokenAddresses, array. Optional.

Output Schema

NameRequiredDescriptionDefault
chainIdNochainId. Number.
sourcesNosources. Array.
snapshotNosnapshot. Object.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
walletAddressNowalletAddress. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds real context beyond them: fixed chain, pricing source, a $0.02 USDC cost, the POST endpoint, and the x402 behavior that an unpaid call returns payment terms instead of running. That payment-failure mode is exactly the kind of detail 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.

Conciseness5/5

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

Four short sentences, front-loaded with the outcome, then the exclusion and routing, then cost/endpoint/payment semantics. Every sentence carries a fact an agent needs, with no hedging or repetition.

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?

Output schema exists, so return values need no explanation, and the description still covers chain scope, pricing source, cost, transport, and payment failure. Minor gap: it does not say how fresh the balance is (live read vs cached), which matters for a portfolio-style snapshot.

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 parameters are already documented. The phrase "supplied token balances" hints that tokenAddresses scopes which tokens are valued, but it adds no format or default detail beyond the schema — baseline 3.

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?

States a specific verb (retrieve) and resource (current wallet balance plus supplied token balances), and pins down scope: Base Mainnet only, USD valuations from DeFiLlama. It also explicitly excludes approvals/allowances, which separates it from the security-approvals sibling.

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?

Gives a clear when-not condition with a named alternative: approvals are not included, so use security/approvals before moving funds. It does not explain when to prefer this over analyze, transfers, or transaction, but the boundary it does draw is explicit and actionable.

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