Skip to main content
Glama

AINDEX

Every Lighter RH perp, scored

market_screener
Read-only

Every perp on Lighter on Robinhood Chain scored -100 to +100 from its trend on 1h and 4h, the day's move in daily ATRs, its strength against BTC (crypto) or QQQ (stocks) over a week, and the volume behind it; with signals (runner, breakout, breakdown, leads or lags, divergence against the move, squeeze or flush risk) and whether the move is real (volume and open interest behind it, both timeframes agreeing).

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

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so credit goes to what the description adds: the scoring range and direction, the exact inputs behind the score (1h/4h trend, daily-ATR move, relative strength vs BTC or QQQ, volume), the signal vocabulary, and the 'is the move real' verdict with volume/open-interest confirmation. It omits how results are ordered and whether the cap truncates the ranked list, which is the main remaining behavioral gap.

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

Conciseness3/5

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

The key claim (every perp, scored -100 to +100) is front-loaded, which is correct. But the remainder is a single semicolon-stacked run-on that mixes methodology, signal names, and a quality verdict, making it harder to parse than a two- or three-sentence split would be.

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 does useful work in sketching the return contents (scores, signals, 'real move' verdict). It still leaves the agent without ordering behavior, pagination/limit semantics, or any sense of result shape, which matters for a ranking tool that an agent may need to slice.

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

Parameters2/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 parameter meaning and largely doesn't: the 'limit' parameter (default 20, max 60) is never mentioned, nor is whether it truncates a ranked list. The 'kind' enum is only obliquely implied by the parenthetical '(crypto)' vs '(stocks)' references to BTC and QQQ, and the description never says which universe 'stock' covers on Robinhood Chain.

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 a concrete resource ('every perp on Lighter on Robinhood Chain') and a concrete output (a -100 to +100 score plus named signals), which is far more specific than a bare title. It does not, however, distinguish itself from lookalike siblings such as get_lighter_markets or market_brief, so an agent must infer the difference from the words 'scored' and the signal list.

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 explicit statement of when to reach for this screener versus market_overview, market_brief, or get_lighter_markets, and no when-not-to-use condition. Usage is only weakly implied by the emphasis on ranking and signals, leaving the agent to guess whether this replaces or supplements the plain market-list tools.

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