Skip to main content
Glama

AINDEX

Trending and new pools on Robinhood Chain

discover_tokens
Read-only

Pools that are trending (GeckoTerminal's ranking over 5m, 1h, 6h or 24h) or newly created, 20 a page, with the base token, liquidity, volume, price change, buyers and age. Most new tokens fail: check get_token_market and simulate a small trade before buying.

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": {
      "list": "<list>"
    },
    "name": "discover_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
listYes
pageNo
durationNo24h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new behavioral detail: 20 results per page, the fields returned (base token, liquidity, volume, price change, buyers, age), and the risk profile of new tokens. It does not state what happens beyond page 5 or whether duration is ignored for the 'new' list, leaving a small gap.

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?

Two tight sentences: the first front-loads what the list is and what each row contains, the second front-loads the risk warning. Every clause carries information an agent would otherwise have to infer.

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 3-parameter read-only discovery tool with no output schema, the definition covers result contents, page size, ranking semantics and safe next steps. Remaining gaps are minor: page semantics and whether duration applies to the 'new' list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load, and it does explain the list and duration semantics ('trending' = ranking over 5m/1h/6h/24h; 'new' = newly created). The page parameter is only indirectly conveyed via '20 a page' and its max of 5 is never mentioned.

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?

Names the resource precisely ('pools that are trending ... or newly created') and discloses the ranking source and its windows, so an agent knows exactly what the list contains. It stops short of differentiating itself by name from the closest siblings (list_pools, search_tokens), so it is clear but not sibling-aware.

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?

Gives a concrete usage context (surface trending vs. newly created pools) plus an explicit follow-up workflow: check get_token_market and simulate a small trade before buying. It offers no exclusions or named alternative for browsing pools that are neither trending nor new, which keeps it just under a 5.

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