Skip to main content
Glama

Get Token Composite AlphaScore, Momentum & Security Analysis

get_token_alpha
Read-onlyIdempotent

Computes a fail-closed 0–100 AlphaScore for a token by combining contract security, volume momentum, buy pressure, liquidity depth, and wash-trading detection.

Instructions

Computes a fail-closed composite AlphaScore (0-100) combining GoPlus smart contract security (40% weight), DexScreener 5m/1h volume momentum & buy-pressure ratio (35% weight), and USD liquidity depth (25% weight) with automatic wash-trading detection. Free to start with zero wallet or setup required (3 free queries/day); unlimited calls supported via optional Base prepaid session.

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_token_alpha"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe token smart contract address (0x... for EVM chains or Base58 mint address for Solana). Example Base token: "0x532f27101965dd16442e59d40670faf5ebb142e4".
networkNoTarget blockchain network: "base", "solana", "ethereum", "bsc", "arbitrum", or "polygon". Defaults to "base".base
paymentProofNoOptional Base USDC transaction hash ("0x...") for high-frequency trading bots needing unlimited calls. Leave empty for automatic free daily queries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.1
    • changedInput schema / properties / paymentProof / description
      Previous value: -"Optional Base USDC transaction hash (\"0x...\") or HTTP 402 payment proof for unlimited calls after your 3 free daily queries. Deposit $1.00 USDC once on Base to 0x8a8c238ed2b46908Ff6C6922a3870984f20f8913 for 50 instant alpha calls."New value: +"Optional Base USDC transaction hash (\"0x...\") for high-frequency trading bots needing unlimited calls. Leave empty for automatic free daily queries."
  2. Changed6 schema fields changedv1.6.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / address / description
      Previous value: -"The smart contract address or token mint address"New value: +"The token smart contract address (0x... for EVM chains or Base58 mint address for Solana). Example Base token: \"0x532f27101965dd16442e59d40670faf5ebb142e4\"."
    • addedInput schema / properties / network / default
      Added value: +"base"
    • changedInput schema / properties / network / description
      Previous value: -"Blockchain network (default is base)"New value: +"Target blockchain network: \"base\", \"solana\", \"ethereum\", \"bsc\", \"arbitrum\", or \"polygon\". Defaults to \"base\"."
    • changedInput schema / properties / network / enum
      Previous value: -[
      -  "base",
      -  "solana",
      -  "ethereum",
      -  "bsc",
      -  "arbitrum",
      -  "polygon"
      -]New value: +[
      +  "base",
      +  "ethereum",
      +  "solana",
      +  "bsc",
      +  "arbitrum",
      +  "polygon"
      +]
    • addedInput schema / properties / paymentProof
      Added value: +{
      +  "description": "Optional Base USDC transaction hash (\"0x...\") or HTTP 402 payment proof for unlimited calls after your 3 free daily queries. Deposit $1.00 USDC once on Base to 0x8a8c238ed2b46908Ff6C6922a3870984f20f8913 for 50 instant alpha calls.",
      +  "type": "string"
      +}
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses fail-closed semantics, wash-trading detection, the weighted scoring model, a concrete quota (3 free queries/day), and the optional Base USDC prepaid path for unlimited calls. It stops short of explaining failure behavior per data source or the shape of the returned score breakdown.

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?

Two sentences, front-loaded with the core computation and weights before the free/prepaid access note. The weight percentages earn their place because they determine how to interpret the score, though the sentence is dense with parenthetical detail.

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?

With no output schema, the description carries the burden of explaining the return value; it gives the 0-100 range, the contributing signals, and fail-closed behavior, which is enough to interpret a result. It does not state what the response actually contains (e.g., per-component breakdown) or what a token returns when a source fails.

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 coverage is 100%, so the schema already documents address, network, and paymentProof thoroughly. The description adds only marginal value, clarifying that the prepaid session is Base-specific and optional, which is essentially a restatement of the paymentProof schema text. Baseline 3 applies.

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?

States a specific verb and resource: computes a composite AlphaScore (0-100) from three explicitly weighted sources (security 40%, momentum 35%, liquidity 25%) plus wash-trading detection. The 'composite' framing implicitly separates it from the sibling check_token_security (security-only) and get_polymarket_alpha, though no sibling is named directly.

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

Usage Guidelines3/5

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

Usage is implied by the composite-scoring description and the note that free queries are automatic while a prepaid session unlocks unlimited calls, but there is no explicit 'use this instead of check_token_security when...' routing. An agent must infer when the full composite is preferable to the narrower security or Polymarket siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.