Skip to main content
Glama

Analyzing token quant scores

token_quant_scores
Read-onlyIdempotent

Get Nansen Score Indicators for a token - quantitative risk and reward signals.

Use this tool when assessing a token's risk/reward profile, evaluating buy/sell decisions, or when the user needs quantitative data to make trading decisions.

Returns: Token risk/reward indicators as markdown with interpretation guidance.

Token info:
- **Market Cap**: Current market cap in USD
- **Market Cap Group**: largecap (>$1B), midcap ($100M-$1B), or lowcap (<$100M)
- **Is Stablecoin**: Whether token is a stablecoin (some indicators don't apply to stablecoins)

Fields returned per indicator:
- **Score**: Signal classification (bullish/neutral/bearish for reward; low/medium/high for risk)
- **Signal**: Raw numeric value of the indicator
- **Percentile**: Rank vs same market cap group (0-100%)
- **Last Trigger**: Date when signal was last calculated

Indicator types:
- **Reward Indicators**: price-momentum, funding-rate, chain-fees, chain-tvl, protocol-fees, trading-range
- **Risk Indicators**: btc-reflexivity, liquidity-risk, token-supply-inflation, concentration-risk, cex-flows

Notes: - Not all indicators available for every token/chain combination - Percentile compares against same market cap group (largecap >$1B, midcap $100M-$1B, lowcap <$100M)

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

Input Schema

NameRequiredDescriptionDefault
requestYesRequest model for Nansen Score Indicators endpoint (flattened).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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 Indicators endpoint (flattened).",
      -    "properties": {
      -      "chain": {
      -        "default": "ethereum",
      -        "description": "Blockchain chain (ethereum, solana, base, bnb, polygon, arbitrum, etc.). On-chain tokens only — Hyperliquid perps NOT supported.",
      -        "type": "string"
      -      },
      -      "tokenAddress": {
      -        "description": "Token contract address",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "tokenAddress"
      -    ],
      -    "type": "object"
      -  }
      -]
    • addedInput schema / properties / request / description
      Added value: +"Request model for Nansen Score Indicators endpoint (flattened)."
    • addedInput schema / properties / request / properties
      Added value: +{
      +  "chain": {
      +    "default": "ethereum",
      +    "description": "Blockchain chain (ethereum, solana, base, bnb, polygon, arbitrum, etc.). On-chain tokens only — Hyperliquid perps NOT supported.",
      +    "type": "string"
      +  },
      +  "tokenAddress": {
      +    "description": "Token contract address",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / request / required
      Added value: +[
      +  "tokenAddress"
      +]
    • addedInput schema / properties / request / type
      Added value: +"object"
  2. Changed3 schema fields changed
    • removedInput schema / $defs
      Removed value: -{
      -  "TokenQuantScoresRequest": {
      -    "description": "Request model for Nansen Score Indicators endpoint (flattened).",
      -    "properties": {
      -      "chain": {
      -        "default": "ethereum",
      -        "description": "Blockchain chain (ethereum, solana, base, bnb, polygon, arbitrum, etc.). On-chain tokens only — Hyperliquid perps NOT supported.",
      -        "type": "string"
      -      },
      -      "tokenAddress": {
      -        "description": "Token contract address",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "tokenAddress"
      -    ],
      -    "type": "object"
      -  }
      -}
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / request / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "$ref": "#/$defs/TokenQuantScoresRequest"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  {
      +    "description": "Request model for Nansen Score Indicators endpoint (flattened).",
      +    "properties": {
      +      "chain": {
      +        "default": "ethereum",
      +        "description": "Blockchain chain (ethereum, solana, base, bnb, polygon, arbitrum, etc.). On-chain tokens only — Hyperliquid perps NOT supported.",
      +        "type": "string"
      +      },
      +      "tokenAddress": {
      +        "description": "Token contract address",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "tokenAddress"
      +    ],
      +    "type": "object"
      +  }
      +]
  3. Changed1 schema field changed
    • changedInput schema / $defs / TokenQuantScoresRequest / properties / chain / description
      Previous value: -"Blockchain chain (ethereum, solana, base, bnb, polygon, arbitrum, etc.)"New value: +"Blockchain chain (ethereum, solana, base, bnb, polygon, arbitrum, etc.). On-chain tokens only — Hyperliquid perps NOT supported."
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, open-world), so the description does not need to re-litigate that. It adds real behavioral context beyond the annotations: indicator coverage is not universal across token/chain combinations, some indicators do not apply to stablecoins, and percentiles are normalized against a market cap group. It does not mention rate limits or data freshness beyond the 'Last Trigger' field, which is why this is a 4 rather than a 5.

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?

The purpose and usage guidance are front-loaded and easy to scan, which is good. However, the long enumerated lists of token info and per-indicator fields largely restate the output schema, and the market cap group thresholds are repeated twice (in 'Market Cap Group' and again in the final note). That redundancy costs space without adding meaning.

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 single-parameter read tool with a full output schema and complete annotations, the description is nearly sufficient: it covers purpose, usage scenarios, availability caveats, and score semantics. Its main inefficiency is duplicating return-value documentation the output schema already provides, while the indicator name list has no explanation of what each indicator means.

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 only one nested request parameter, so the schema already carries the parameter meaning, including the chain constraint that Hyperliquid perps are unsupported. The description adds nothing about chain or tokenAddress and never mentions the request object. Baseline 3 applies when the schema does the work.

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 first line gives a specific verb and resource: 'Get Nansen Score Indicators for a token - quantitative risk and reward signals.' That is clear enough that an agent can distinguish it from sibling quantitative tools such as token_technical_indicators. However, the description never names or contrasts any sibling, so the differentiation is implied rather than stated.

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

Usage Guidelines4/5

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

It states concrete when-to-use conditions: assessing a token's risk/reward profile, evaluating buy/sell decisions, or when the user needs quantitative data for trading decisions. What is missing is any exclusion or alternative, such as when to prefer technical indicators or flows data instead. This is clear context without 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