Skip to main content
Glama

Trending tokens

trending_tokens
Read-only

Get top trending/boosted tokens on DEXScreener. Shows what's getting the most attention right now. Optionally filter by chain. Costs $0.002 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trending_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoFilter by chain (e.g. 'solana', 'ethereum', 'base'). Omit for all chains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: the upstream source (DEXScreener) and a concrete per-call price of $0.002 USDC, which matters for cost-aware agents. It stops short of describing result size or return shape.

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

Conciseness5/5

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

Three short sentences with zero filler: what it returns, what it means, and what it costs. The core purpose is front-loaded and the cost caveat is placed last, which is appropriate.

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?

A one-parameter read tool with annotations and no output schema needs only a clear purpose, source, and cost, all of which are present. The notable omission is result cardinality/ranking basis – how many tokens come back and how 'trending' is measured – which an agent would want for a ranked-list 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% and the single 'chain' parameter is fully documented with examples in the schema itself. The description only restates that the filter is optional and defaults to all chains, adding no syntax or format detail beyond the structured field. Baseline 3 applies.

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?

States a specific verb and resource coupled to a named data source: 'Get top trending/boosted tokens on DEXScreener.' This clearly separates it from siblings like new_pairs or dex_search, though it doesn't explicitly contrast itself with those tools.

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?

'Shows what's getting the most attention right now' implies a real-time attention/ranking use case, and the chain filter is framed as optional. But there is no explicit when-to-use versus alternatives such as new_pairs or prediction_markets_trending, and no exclusions.

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