Skip to main content
Glama

DeFade — Multi-Chain Memecoin Analyzer

First-block snipers

get_launch_snipers
Read-onlyIdempotent

Bots that bought in the first block or first seconds of this token's launch, and whether they are connected to the deployer. The window is the first 120 seconds after the first transaction; at most 30 rows are returned and totalEarlyBuyers carries the full count. Migration-crank MEV bots are excluded and named rather than silently dropped. Check reachedGenesis: when false the walk did not reach the true first transaction, the result is partial, and it is cached for an hour instead of two. Use it to tell an organic launch from a pre-arranged one. Not for coordinated multi-wallet launch buying (get_launch_bundles) or the deployer's funding of other wallets (get_wallet_links). Arguments: address and chain; one API unit on any chain.

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

Input Schema

NameRequiredDescriptionDefault
chainNoChain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm, monad, elysium. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan.solana
addressYesThe token's own contract address, exactly as an explorer shows it. Solana: the base58 mint, 32-44 characters (e.g. 6p6xgHyF7AeE6TZkSmFsko444wqoP15icUSqi2jfGiPN). EVM: 0x followed by 40 hex characters, case-insensitive (e.g. 0x6982508145454ce325ddbe47a25d4ec3d2311933). Never a pool, pair, wallet or deployer address — those come back as not found. Set `chain` to match the address: a 0x address alone cannot say which EVM chain it lives on, and a Solana mint sent with an EVM chain is rejected.

Output Schema

NameRequiredDescriptionDefault
statsNoCohort totals for the window. stats.transferredUnsoldPct is the transferred share the DeFade website prints; the gross transfer figures count a token each time it moved. Solana: stats.bundleCohort is false when no bundle scan had run, so transfers to bundle wallets read as transferred supply.
tokenNoThe address that was scanned (on get_token_scan, the full token metadata object instead).
pendingNoSolana: ["bundles-pro"] when this was read before Bundle Detection had run; the call started it. Call again in about a minute for the answer the scan page shows.
snipersNoWallets that bought inside the launch window, capped at 30 rows.
completeNoFalse beside pending.
poweredByNoAlways "DeFade.org".
terminalsNoTrading terminals the launch cohort came through; activeTerminals is who trades it now.
timestampNoISO time the response was assembled.
reachedGenesisNoWhether the walk reached the true first transaction. When false, partial is true and small snipers may be missing.
totalEarlyBuyersNoHow many were found in total; windowSeconds and firstTxTime describe the window.
migrationCrankersExcludedNoMigration-crank MEV bots filtered out as infrastructure, named.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm, monad. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."New value: +"Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm, monad, elysium. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "solana",
      -  "ethereum",
      -  "base",
      -  "bsc",
      -  "robinhood",
      -  "arc",
      -  "hyperevm",
      -  "monad"
      -]New value: +[
      +  "solana",
      +  "ethereum",
      +  "base",
      +  "bsc",
      +  "robinhood",
      +  "arc",
      +  "hyperevm",
      +  "monad",
      +  "elysium"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."New value: +"Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm, monad. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "solana",
      -  "ethereum",
      -  "base",
      -  "bsc",
      -  "robinhood",
      -  "arc",
      -  "hyperevm"
      -]New value: +[
      +  "solana",
      +  "ethereum",
      +  "base",
      +  "bsc",
      +  "robinhood",
      +  "arc",
      +  "hyperevm",
      +  "monad"
      +]
  3. Changed1 schema field changed
    • changedOutput schema / properties / stats / description
      Previous value: -"Cohort totals for the window. Solana: stats.bundleCohort is false when no bundle scan had run, so transfers to bundle wallets read as transferred supply."New value: +"Cohort totals for the window. stats.transferredUnsoldPct is the transferred share the DeFade website prints; the gross transfer figures count a token each time it moved. Solana: stats.bundleCohort is false when no bundle scan had run, so transfers to bundle wallets read as transferred supply."
  4. Changed3 schema fields changed
    • addedOutput schema / properties / complete
      Added value: +{
      +  "description": "False beside pending.",
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / pending
      Added value: +{
      +  "description": "Solana: [\"bundles-pro\"] when this was read before Bundle Detection had run; the call started it. Call again in about a minute for the answer the scan page shows.",
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / stats / description
      Previous value: -"Cohort totals for the window."New value: +"Cohort totals for the window. Solana: stats.bundleCohort is false when no bundle scan had run, so transfers to bundle wallets read as transferred supply."
  5. Changed2 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"Chain the token is deployed on: solana (default), ethereum, base, robinhood. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."New value: +"Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "solana",
      -  "ethereum",
      -  "base",
      -  "robinhood"
      -]New value: +[
      +  "solana",
      +  "ethereum",
      +  "base",
      +  "bsc",
      +  "robinhood",
      +  "arc",
      +  "hyperevm"
      +]
  6. Changed8 schema fields changed
    • changedOutput schema / properties / migrationCrankersExcluded / type
      Previous value: -"array"New value: +[
      +  "array",
      +  "null"
      +]
    • changedOutput schema / properties / poweredBy / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / reachedGenesis / type
      Previous value: -"boolean"New value: +[
      +  "boolean",
      +  "null"
      +]
    • changedOutput schema / properties / snipers / type
      Previous value: -"array"New value: +[
      +  "array",
      +  "null"
      +]
    • changedOutput schema / properties / stats / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / terminals / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / timestamp / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / totalEarlyBuyers / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
  7. Added

TDQS

A4.6/5.0
Behavior5/5

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

Well beyond the readOnly/idempotent annotations, it discloses the sampling window (first 120 seconds after the first transaction), a row cap of 30 with totalEarlyBuyers carrying the full count, that migration-crank MEV bots are excluded and named rather than silently dropped, and the partial-result semantics via reachedGenesis plus a caching difference (one hour vs two). It also states the cost (one API unit on any chain). This is unusually rich behavioral context for a read tool.

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?

It is dense but front-loaded: the resource, scope, output caveats, and sibling routing each add distinct value. The one weak clause is the redundant "Arguments: address and chain" summary before the cost note, which repeats structured data. Overall tight with minimal waste.

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?

Even though an output schema exists (so return values needn't be explained), the description proactively clarifies key return fields (totalEarlyBuyers, reachedGenesis) and their interpretation, plus the caching implication. Combined with full schema coverage and annotations, an agent has everything needed to call this correctly and interpret partial results.

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%, with both address and chain fully documented in the schema (including format, chain-matching rules, and enum). The description's trailing summary "Arguments: address and chain" largely restates the schema, adding only the API-unit cost, which is behavioral rather than parameter meaning. Baseline 3 applies since the schema carries the semantic load.

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 specific noun phrase naming the exact subject: "Bots that bought in the first block or first seconds of this token's launch, and whether they are connected to the deployer." It then narrows the scope (120-second window) and explicitly distinguishes from siblings get_launch_bundles and get_wallet_links, so an agent can tell exactly what this tool returns and what it does not.

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?

It gives an explicit positive use case ("Use it to tell an organic launch from a pre-arranged one") and explicit exclusions that name the alternatives: coordinated multi-wallet launch buying goes to get_launch_bundles, and deployer funding of other wallets goes to get_wallet_links. Nothing about selection is left to inference.

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