Skip to main content
Glama
monsterbyurbed11

Alpha402

by monsterbyurbed11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Token Composite AlphaScore, Momentum & Security Analysis

get_token_alpha
Read-onlyIdempotent

Computes a fail-closed AlphaScore (0-100) from contract security, volume momentum, buy pressure, and liquidity depth to detect wash trading and assess token risk.

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. Includes 3 free calls/day; unlimited calls cost $0.02 USDC.

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...") 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish that this is a safe, idempotent read operation, and the description adds substantial behavioral context beyond that: fail-closed scoring, component weights, wash-trading detection, free daily quota, and paid unlimited-call mechanics. The main residual gap is that "fail-closed" is not further explained, and the exact result format is not described.

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 two sentences and front-loads the core capability before pricing details. The first sentence is dense with component weights, but those details are relevant to understanding the score, and there is little wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a high-complexity scoring and payment tool, and while the description covers the score composition and payment model, it does not explain the return structure or how fail-closed behavior manifests in results. With no output schema, the description should carry more of the return-value burden than it does.

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%, and all three parameters are already documented in the schema, including the address formats, network enum, and paymentProof purpose. The description adds general pricing and payment context but no meaningful parameter-level detail beyond what the schema provides, so the baseline 3 is appropriate.

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?

The description states a specific verb and resource: it computes a composite AlphaScore for a token, with named components (GoPlus security, DexScreener momentum, liquidity depth) and a 0-100 scale. It is clearly about a composite scoring tool, but it does not explicitly distinguish this from sibling tools such as check_token_security or get_new_pairs_alpha.

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

Usage Guidelines2/5

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

The description explains what the score contains and the pricing model, but gives no explicit guidance on when to use this tool versus check_token_security or get_new_pairs_alpha. There are no exclusions or conditions that would route an agent between the siblings.

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

Deploy Server

Other Tools