Skip to main content
Glama

token_research

Read-onlyIdempotent

Multi-source token intelligence: market data, DeFi metrics, contract verification, prediction markets, holder analysis, price history, and AI risk assessment. Aggregates CoinGecko, DeFiLlama, Etherscan, and Polymarket. 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": {
      "query": "<query>"
    },
    "name": "token_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain networkethereum
queryYesToken name, symbol, or contract address
includeNoData modules to include (default: market_data, defi_metrics, contract_info, risk_assessment)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already establish that this is read-only, idempotent, open-world, and non-destructive. The description adds useful behavior beyond annotations by naming the aggregated data providers and explaining the free-call limit and pay-per-call fallback after 10 calls per day.

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 front-loaded with the tool's purpose and uses two efficient sentences. The module list is dense but relevant, and the quota/paywall sentence earns its place by disclosing an important operational constraint.

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?

For a multi-source aggregator with no output schema, the description covers the data domains, providers, and quota behavior. It still does not describe the return shape, how module results are combined, or how partial failures are handled, which leaves meaningful gaps for a complex research 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%, so the input schema already defines chain, query, and include with enum values and defaults. The description lists the data categories that correspond to include modules, but it does not add syntax or interpretation beyond the schema, so 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 gives a specific resource and scope: multi-source token intelligence covering market data, DeFi metrics, contract verification, prediction markets, holder analysis, price history, and risk assessment. It clearly says what the tool does, but it does not distinguish itself from sibling tools such as token_intel, token_compare, or token_risk_metrics.

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 for comprehensive token research, and the description adds a concrete operational guideline about the free MCP quota and x402 pay-per-call fallback. However, it gives no explicit when-to-use guidance versus the many sibling token and risk tools, so an agent must infer the routing decision.

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.