Skip to main content
Glama

AINDEX

Relative strength scan

performance_scanner
Read-only

Rank markets by return over a window against a benchmark (BTC for crypto, SPY for stocks; QQQ shown too): every Lighter on Robinhood Chain perp, Hyperliquid's 40 most traded perps, or the stocks with a Robinhood token. Leaders and laggards with relative strength.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
windowNo7d
universeNolighter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish this as a safe external read, so the bar is lower. The description adds useful context the annotations don't carry: which benchmark each universe is measured against (BTC, SPY, QQQ) and that the Hyperliquid universe is capped at 40 most-traded perps. It omits ordering/return shape and whether limit truncates leaders vs laggards.

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?

The main action is front-loaded in the first clause, with universes and benchmark details following. Dense but largely waste-free, though the stacked parentheticals ("BTC for crypto, SPY for stocks; QQQ shown too") and trailing fragment "Leaders and laggards with relative strength" make it slightly harder to parse than it needs to 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 should describe what comes back, and it only gestures at it ("Leaders and laggards with relative strength") without specifying fields, sort order, or result count. For a three-parameter screening tool this is adequate but leaves the agent guessing about response structure and truncation behavior.

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 0%, so the description must compensate and it only partly does. It explains the otherwise opaque 'universe' enum values (every Lighter perp, 40 top Hyperliquid perps, tokenized Robinhood stocks) and clarifies 'window' as the return lookback, but says nothing about 'limit' (5-60, default 20) or how it interacts with returning both leaders and laggards.

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 opens with a specific verb and resource: "Rank markets by return over a window against a benchmark." It then enumerates the three universes and names the benchmarks, so an agent can distinguish a relative-strength ranking from sibling lookups like get_lighter_markets or get_derivatives. It stops short of naming an alternative explicitly, which keeps it below 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?

Usage is implied by the phrase "Leaders and laggards with relative strength," which signals the tool is for finding outperformers and underperformers. There is no explicit when-to-use/when-not guidance and no routing to a sibling for a different comparison (e.g. raw returns without a benchmark). The agent must infer the right context.

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