Skip to main content
Glama

Aevum: verified trading records

Check a prop firm's payouts

check_payout_wallet
Read-only

Stablecoin payouts a wallet has actually sent, from public block explorers: total, number of transfers, median and largest, how many different wallets received them, repeat recipients, how concentrated they are, the last 30 days, month by month for a year, and days since the last transfer. Built for prop firm payout wallets ('does this firm really pay?'). Ethereum, Arbitrum, Base, Polygon (USDC/USDT) or Tron (USDT, T... address). These are on-chain transfers, not Aevum calls: they can include affiliate, vendor or internal transfers, and nothing confirms who owns the wallet.

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

Input Schema

NameRequiredDescriptionDefault
addressYesPayout wallet: 0x + 40 hex (EVM) or a Tron address starting with T

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint and openWorldHint, it discloses which chains and tokens are supported, the metric set returned, and important interpretive caveats: transfers may include affiliate, vendor or internal transfers, and nothing confirms wallet ownership. That is exactly the kind of context annotations cannot convey.

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?

The description is front-loaded with the outcome (what the wallet actually paid out) followed by coverage and caveats; every sentence adds information. The long metric enumeration is dense and slightly run-on, keeping it just below a 5.

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, but the description effectively compensates by listing the returned metrics (total, count, median, largest, unique recipients, repeat recipients, concentration, 30-day, 12-month, days since last transfer). For a single-parameter read tool, nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents the 0x/Tron address format, so the baseline is 3. The description adds supported networks (Ethereum, Arbitrum, Base, Polygon, Tron) and asset types (USDC/USDT), which meaningfully constrains valid inputs beyond the schema.

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 opens with a precise verb+resource ('Stablecoin payouts a wallet has actually sent, from public block explorers') and enumerates the returned metrics, so an agent can distinguish it from check_hyperliquid_wallet or check_polymarket_wallet and from Aevum-internal record tools.

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 states a clear use case ('Built for prop firm payout wallets — does this firm really pay?') and explicitly separates it from Aevum calls ('These are on-chain transfers, not Aevum calls'). It does not name a sibling alternative or an explicit when-not-to-use condition, so it falls short of a 5.

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