Skip to main content
Glama

token_risk_metrics

Read-onlyIdempotent

Quantitative risk metrics for any ERC-20 token: holder concentration (top 10 holder %), contract permissions (can mint/burn/pause/blacklist), liquidity depth vs market cap, deployer history, and weighted composite risk score (0-100). Pre-computed for top tokens, live-computed for others. Free over MCP for 10 calls per day; beyond that the tool returns the pay-per-call x402 endpoint and its price.

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

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain networkethereum
addressYesToken contract address (0x-prefixed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "ethereum",
      -  "base",
      -  "arbitrum",
      -  "optimism",
      -  "polygon",
      -  "bsc",
      -  "avalanche",
      -  "linea",
      -  "unichain",
      -  "sonic"
      -]New value: +[
      +  "ethereum",
      +  "base",
      +  "arbitrum",
      +  "optimism",
      +  "polygon",
      +  "bsc",
      +  "avalanche",
      +  "linea",
      +  "unichain",
      +  "sonic",
      +  "hyperevm"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "ethereum",
      -  "base",
      -  "arbitrum",
      -  "optimism",
      -  "polygon"
      -]New value: +[
      +  "ethereum",
      +  "base",
      +  "arbitrum",
      +  "optimism",
      +  "polygon",
      +  "bsc",
      +  "avalanche",
      +  "linea",
      +  "unichain",
      +  "sonic"
      +]
  3. First observed

TDQS

A4.1/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, openWorld), so the description's job is added context — and it delivers: pre-computed vs live-computed results, a hard free-tier ceiling, and the exact fallback behavior (returns an x402 endpoint plus price) once the quota is exceeded. That quota/payment behavior is not derivable from any structured field.

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?

Front-loaded with the capability, then the metric list, then the quota/payment caveat — a logical order with no filler sentences. The metric enumeration is dense but each item is informative rather than decorative.

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?

There is no output schema, and the description does the necessary work by naming the returned metrics and the 0-100 score range, plus the rate-limit fallback response. It stops short of describing response shape/nesting or what the agent should do when an x402 endpoint is returned, which would fully close the loop for a paid-fallback tool.

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 the address pattern and the chain enum fully documented, so the schema carries parameter meaning. The description adds only the ERC-20 constraint on the address (implying non-ERC-20/cross-VM tokens are out of scope) and says nothing about chain selection or defaults beyond what the enum provides; baseline 3 is appropriate.

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+resource ('Quantitative risk metrics for any ERC-20 token') and then enumerates the exact metric families returned: holder concentration, contract permissions, liquidity depth vs market cap, deployer history, and a 0-100 composite score. The ERC-20 scoping also implicitly separates it from Solana-oriented siblings like solana_token_risk_scan.

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?

It gives clear operational context (free for 10 calls/day, beyond that the x402 pay-per-call endpoint and price are returned), which tells the agent what to expect on repeat use. However, it never says when to pick this over token_intel, token_research, or token_compare, nor does it state prerequisites for the address beyond ERC-20.

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.