Skip to main content
Glama

List trending coins

list_trending_coins
Read-only

Discover trending Robinhood Chain pools (memecoins and stocks) with price, 24h volume, price change, and liquidity to gauge current market activity.

Instructions

The trending pools on Robinhood Chain right now (memecoins and stocks) with price, 24h volume, price change, and liquidity — the pulse of the chain.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many (default 10, max 30).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context by enumerating the returned metrics and implying a live snapshot ('right now'), but it does not disclose ranking criteria, ordering, or whether data is cached/refreshed, which matters for an open-world live-data tool.

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?

One sentence, front-loaded with the resource and scope, with the data fields listed compactly. The trailing tagline 'the pulse of the chain' is decorative rather than informative but costs only a few words.

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?

With no output schema, the description must convey the return values; it lists the metrics but not the structure (e.g., per-pool entries with token identity or chain identifiers), and it leaves 'trending' undefined. Adequate for a simple one-parameter read tool, but not fully self-sufficient.

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?

The single 'limit' parameter is fully documented in the schema (default 10, max 30, exclusiveMinimum 0), so schema coverage is 100% and the description adds nothing about it. Baseline 3 applies since the schema carries the entire parameter burden.

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 names the resource (trending pools on Robinhood Chain), the asset classes covered (memecoins and stocks), and the data fields returned (price, 24h volume, price change, liquidity). It is specific enough for an agent to know this is a trending-markets read, though it never distinguishes itself from siblings like get_recent_launches or list_stock_tokens, and the name/description mismatch ('coins' vs 'pools') adds slight ambiguity.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives. An agent gets no explicit signal for choosing this over get_recent_launches (new listings) or list_stock_tokens, nor any explanation of what qualifies a pool as 'trending' or how results are ranked.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.