Skip to main content
Glama

Crypto & Macro Market Data (Tanod)

get_large_token_trades

Read-onlyIdempotent

chainpeek: Who is buying this token? Recent large trades: big buys and sells on Base or Ethereum. For Solana use get_large_solana_token_trades; for a quote at your size use get_swap_quote. Returns who bought and sold an ERC-20 in size: the recent large buys and sells of it on Base or Ethereum from DEX swap events (Uniswap V2/V3, Aerodrome): time, side, token amount, USD size, the transaction sender's wallet, tx hash and pool, newest first, at most 50. Size-based only, no wallet is labelled; read from swap events of the top 3 pools, so it can miss trades elsewhere; amounts are heuristic; a bad address or a window over 60 minutes (Base) or 240 (Ethereum) is a 422 (not charged); Base logs reach about 27 min back (window.complete); cached 30 s. Typically 3 to 6 s (pool discovery, header and log reads, senders), at most 25 s. Price: USD 0.01. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/token-large-trades-api.html

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": {
      "token": "<token>"
    },
    "name": "get_large_token_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobase (default) or ethereum.base
tokenYesERC-20 token address (0x + 40 hex).
min_usdNoSmallest trade to report, in USD of the quote side (default 1000, minimum 100).
window_minutesNoHow far back to read, in minutes. At most 60 on Base and 240 on Ethereum. The window is cut by block times; public nodes serve logs only about 8,000 blocks deep (about 27 minutes on Base), so a longer Base window is read as its newest 8,000 blocks and `window` says what was read.

Output Schema

NameRequiredDescriptionDefault
noteNo
blockNo
chainNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
poolsNo
tokenNo
cachedNo
reasonNo
tradesNo
windowNo
eth_usdNo
min_usdNo
decimalsNo
returnedNo
truncatedNo
trade_countNo
swaps_scannedNo
wallets_unavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / properties / chain / title
      Removed value: -"Chain"
    • removedInput schema / properties / min_usd / title
      Removed value: -"Min Usd"
    • removedInput schema / properties / token / title
      Removed value: -"Token"
    • changedInput schema / properties / window_minutes / description
      Previous value: -"How far back to read, in minutes (default 60). At most 60 on Base and 240 on Ethereum. The window is cut by block times; public nodes serve logs only about 8,000 blocks deep (about 27 minutes on Base), so a longer Base window is read as its newest 8,000 blocks and `window` says what was read."New value: +"How far back to read, in minutes. At most 60 on Base and 240 on Ethereum. The window is cut by block times; public nodes serve logs only about 8,000 blocks deep (about 27 minutes on Base), so a longer Base window is read as its newest 8,000 blocks and `window` says what was read."
    • removedInput schema / properties / window_minutes / title
      Removed value: -"Window Minutes"
    • removedInput schema / title
      Removed value: -"get_large_token_tradesArguments"
    • removedOutput schema / properties / pools / items
      Removed value: -{
      -  "properties": {
      -    "address": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "dex": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "fee_tier": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "liquidity_usd": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "quote_asset": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "stable": {
      -      "type": [
      -        "boolean",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / trades / items
      Removed value: -{
      -  "properties": {
      -    "block": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "dex": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "pool": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "side": {
      -      "enum": [
      -        "buy",
      -        "sell",
      -        null
      -      ]
      -    },
      -    "time": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "timestamp": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "token_amount": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "token_amount_raw": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "tx": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "usd": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "wallet": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / window / properties
      Removed value: -{
      -  "blocks": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "complete": {
      -    "type": [
      -      "boolean",
      -      "null"
      -    ]
      -  },
      -  "from_block": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "from_time": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "minutes": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "requested_from_time": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "seconds": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "stopped": {
      -    "enum": [
      -      null,
      -      "chunk_cap",
      -      "rpc_refused_older_blocks"
      -    ]
      -  },
      -  "to_block": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "to_time": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
  2. Changed5 schema fields changed
    • changedInput schema / properties / window_minutes / description
      Previous value: -"How far back to read, in minutes (default 60). At most 60 on Base and 240 on Ethereum, so that the window fits one eth_getLogs read of at most 2,000 blocks per pool."New value: +"How far back to read, in minutes (default 60). At most 60 on Base and 240 on Ethereum. The window is cut by block times; public nodes serve logs only about 8,000 blocks deep (about 27 minutes on Base), so a longer Base window is read as its newest 8,000 blocks and `window` says what was read."
    • addedOutput schema / properties / window / properties / complete
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / window / properties / requested_from_time
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / window / properties / seconds
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / window / properties / stopped
      Added value: +{
      +  "enum": [
      +    null,
      +    "chunk_cap",
      +    "rpc_refused_older_blocks"
      +  ]
      +}
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/open-world, but the description adds substantially more: coverage is limited to the top 3 pools so trades elsewhere are missed, amounts are heuristic, no wallet labelling, a bad address or oversized window is a 422 that is not charged, Base logs only reach ~27 minutes (window.complete flag), results are cached 30 s, latency is 3–6 s typical / 25 s max, and pricing/free-tier limits are stated.

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?

Front-loads the purpose and the sibling routing in the first two sentences, then packs limits, errors, latency and pricing into one dense block. Every clause carries operational value, though the opening rhetorical question and the long run-on middle sentence make it less scannable than it could be.

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?

For a read tool with four parameters, an output schema and annotations, this is complete: it covers coverage caveats, error behavior, freshness, latency, cost and sibling alternatives. An agent could call it correctly and interpret results without reading the docs link.

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%, so the schema already defines all four parameters. The description still adds meaning: the per-chain window caps (60 Base / 240 Ethereum), the ~8,000-block public-node limit that truncates longer Base windows, and that min_usd is measured on the quote side. It stops short of explaining the default min_usd or the address pattern, which the schema covers.

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 and resource ('recent large trades ... big buys and sells ... on Base or Ethereum') and immediately scopes the answer to 'who is buying this token' for ERC-20s. It explicitly distinguishes itself from get_large_solana_token_trades and get_swap_quote by naming the conditions under which each is correct.

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

Usage Guidelines5/5

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

Gives explicit routing: use the Solana variant for Solana tokens, use get_swap_quote for a quote at a given size. It also implies the when-not condition through the size threshold and chain enum. Little inference is required to decide whether this is the right tool.

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.