Skip to main content
Glama

Ranking top tokens by Nansen Score

nansen_score_top_tokens
Read-onlyIdempotent

Discover and filter a daily list of attractive tokens using Nansen Score Indicators weighted by coefficients (= Performance Score).

Use this tool when you don't know which tokens to buy and need recommendations based on backtested indicators. For specific token analysis (e.g., "should I buy AAVE?"), use token_quant_scores instead.

When to use this tool vs token_discovery_screener:

  • Use this tool when you want pre-scored buying recommendations without specifying criteria. It answers "what should I buy?" by returning tokens that already meet a quantitative buying threshold (Performance Score ≥15) based on alpha indicators like price momentum, chain fees, and protocol fees. Data is updated in batches.

  • Use token_discovery_screener when you want live data or to explore tokens by specific criteria like sectors (e.g., "AI memecoins"), token age (e.g., "new launches"), smart money activity, or custom volume/liquidity thresholds. It's a filtering tool with real-time metrics where you define what you're looking for.

Returns tokens pre-filtered by: performance_score >= 15 (buying threshold).

Example queries: "what tokens should I buy?", "which tokens look good?", "best tokens to buy today"

Scoring:

  • Performance Score (range -60 to +75): Higher = better alpha opportunity. Buy threshold: ≥15

  • Risk Score (range -60 to +80): Higher = safer token. >0 indicates low to medium risk.

Every time you give the Performance Score to the user, explain the scoring thresholds above. Same for the Risk Score. Every time quote the underlying indicators that contributed the most to the Performance/ Risk score and recall their definition to the user.

Returns: A list of tokens with the highest Performance Score as markdown.

Core fields: Token Address, Token Symbol, Chain, Performance Score, Risk Score.
Indicator columns are included dynamically based on data availability (columns with all zeros are excluded).

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": {
      "request": "<request>"
    },
    "name": "nansen_score_top_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesRequest model for Nansen Score Top Tokens endpoint (flattened).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / request / additionalProperties
      Added value: +false
    • removedInput schema / properties / request / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "description": "Request model for Nansen Score Top Tokens endpoint (flattened).",
      -    "properties": {
      -      "marketCapGroup": {
      -        "anyOf": [
      -          {
      -            "enum": [
      -              "lowcap",
      -              "midcap",
      -              "largecap"
      -            ],
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "description": "Filter by market cap group: 'lowcap' (<$100M), 'midcap' ($100M-$1B), 'largecap' (>$1B). Default: all groups"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]
    • addedInput schema / properties / request / description
      Added value: +"Request model for Nansen Score Top Tokens endpoint (flattened)."
    • addedInput schema / properties / request / properties
      Added value: +{
      +  "marketCapGroup": {
      +    "anyOf": [
      +      {
      +        "enum": [
      +          "lowcap",
      +          "midcap",
      +          "largecap"
      +        ],
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ],
      +    "default": null,
      +    "description": "Filter by market cap group: 'lowcap' (<$100M), 'midcap' ($100M-$1B), 'largecap' (>$1B). Default: all groups"
      +  }
      +}
    • addedInput schema / properties / request / type
      Added value: +"object"
  2. Changed3 schema fields changed
    • removedInput schema / $defs
      Removed value: -{
      -  "NansenScoreTopTokensRequest": {
      -    "description": "Request model for Nansen Score Top Tokens endpoint (flattened).",
      -    "properties": {
      -      "marketCapGroup": {
      -        "anyOf": [
      -          {
      -            "enum": [
      -              "lowcap",
      -              "midcap",
      -              "largecap"
      -            ],
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "description": "Filter by market cap group: 'lowcap' (<$100M), 'midcap' ($100M-$1B), 'largecap' (>$1B). Default: all groups"
      -      }
      -    },
      -    "type": "object"
      -  }
      -}
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / request / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "$ref": "#/$defs/NansenScoreTopTokensRequest"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  {
      +    "description": "Request model for Nansen Score Top Tokens endpoint (flattened).",
      +    "properties": {
      +      "marketCapGroup": {
      +        "anyOf": [
      +          {
      +            "enum": [
      +              "lowcap",
      +              "midcap",
      +              "largecap"
      +            ],
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "description": "Filter by market cap group: 'lowcap' (<$100M), 'midcap' ($100M-$1B), 'largecap' (>$1B). Default: all groups"
      +      }
      +    },
      +    "type": "object"
      +  }
      +]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavior on top: the hard performance_score >= 15 pre-filter, batch-updated rather than live data, numeric ranges for Performance Score (-60 to +75) and Risk Score (-60 to +80) with their thresholds, and dynamic indicator columns. It also discloses presentation obligations (explain thresholds and quote top contributing indicators), which is behavior an agent cannot infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well front-loaded and clearly sectioned with bold headers, but the Performance Score >= 15 threshold is restated three separate times (comparison bullet, standalone 'Returns tokens pre-filtered by' line, and the Scoring section), and the agent-directed presentation instructions add bulk that is not selection guidance. Trimming the duplicate threshold lines would lose nothing.

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?

For a one-parameter read-only ranking tool this is essentially complete: purpose, alternatives, thresholds, and result shape are all covered, and an output schema exists so return values need not be spelled out. The one omission is the marketCapGroup filter, which an agent would only learn by opening the schema.

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% and the single marketCapGroup parameter is fully documented in the schema, including the lowcap/midcap/largecap dollar cutoffs. The description only gestures at filtering ('Discover and filter') without naming market cap grouping or adding meaning beyond the enum, so the baseline 3 applies.

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 — 'discover and filter a daily list of attractive tokens' scored by Nansen Score Indicators — and immediately pins down what the output means (pre-filtered at Performance Score >= 15). It is explicitly distinguished from both token_quant_scores (single-token analysis) and token_discovery_screener (live criteria-based filtering).

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 an explicit when-to-use ('you don't know which tokens to buy'), an explicit when-not with the correct alternative ('should I buy AAVE?' -> token_quant_scores), and a head-to-head comparison against token_discovery_screener covering both the pre-scored-recommendation case and the live/criteria case. Example queries reinforce the routing.

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