Skip to main content
Glama

AINDEX

Tokens on Robinhood Chain, screened

screen_universe
Read-only

Tokens on Robinhood Chain that AINDEX prices (Robinhood stock and ETF tokens, crypto, stablecoins, Arcus pTokens), with address, price, 24h and 7d change, pool liquidity, 24h volume and earnings within 7 days. Filter by kind, keep those with at least minLiquidityUsd of pool liquidity, and sort by the 24h or 7d move (largest either way), liquidity, volume, or earnings date. Built once a minute.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
sortNoliquidity
limitNo
minLiquidityUsdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data scope are covered. The description adds genuinely new behavioral context: 'Built once a minute' discloses data freshness/lag, and the field list discloses the shape of each result row despite no output schema existing. Auth, rate limits, and pagination behavior remain unstated.

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?

It opens with the identifying scope, then lists contents and sorting options in one compact flow with no filler. Every clause carries information an agent would otherwise have to guess.

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?

With no output schema, the description compensates by enumerating the returned metrics and by stating the refresh cadence. Combined with annotations covering read-only external access, an agent has enough to call this correctly, though the limit default/cap is left implicit.

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 carries the burden and largely does: kind is clarified by the enumerated token categories, minLiquidityUsd is defined as a pool-liquidity floor, and sort is expanded (24h/7d move 'largest either way', liquidity, volume, or earnings date). The limit parameter and its 40 cap are left unexplained, keeping it from a 5.

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 precisely — tokens on Robinhood Chain that AINDEX prices — and enumerates the included categories (stock/ETF tokens, crypto, stablecoins, Arcus pTokens) plus the returned fields. That is far more specific than the title. It does not explicitly contrast itself with siblings like discover_tokens or search_tokens, so it stops short of a 5.

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?

The description explains how to drive the tool (filter by kind, threshold on minLiquidityUsd, choose a sort key) which implies the screening use case. However, it never states when to prefer this over the token-discovery siblings or what conditions make it inappropriate, so usage is inferred rather than prescribed.

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