Skip to main content
Glama

Crypto Derivatives Data API

Perp screener (every perpetual, sorted)

perp_screener
Read-only

Perp screener for all coins: every perpetual future on Bybit, Hyperliquid, dYdX, Gate, Kraken, Bitfinex, Deribit and OKX in one call, sorted by funding rate (APR), open interest (OI), 24h volume or 24h change, with the highest and lowest funding views. A funding screener and perpetuals market ranking for BTC, ETH, SOL and hundreds of altcoins. Data only. Bad input is free; under 3 venues not charged. Empty filter results are still charged. Price: $0.005 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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

Input Schema

NameRequiredDescriptionDefault
sortNofunding | oi | volume | change. Default funding.
limitNoCoins returned, 1-200. Default 50.
orderNoDefault desc.
min_volume_usdNoMinimum total 24 h volume (USD). Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the read-only, open-world profile, and the description adds substantial context beyond them: a per-call price, the x402/USDC-on-Base payment requirement with the exact _meta key, and billing edge cases for bad input and empty results. It does not disclose return shape, data freshness, or pagination semantics, so it stops short of a 5.

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 core capability and payment model are front-loaded and the sentences carry real information. However, the middle sentence ('A funding screener and perpetuals market ranking for BTC, ETH, SOL and hundreds of altcoins') is keyword padding that restates the first sentence, and the venue list is long for the value it adds.

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?

Given four optional parameters and no output schema, the definition covers inputs, cost, and payment adequately, so an agent can invoke it. It leaves two meaningful gaps: it never describes what a result row contains, and 'with the highest and lowest funding views' is never resolved into concrete parameter behavior, leaving ambiguity about whether one call returns two ranked sets.

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 coverage is 100%, so sort, limit, order, and min_volume_usd are already fully documented with ranges, enums, and defaults, making baseline 3 appropriate. The description restates the sort keys and hints at an 'highest and lowest funding views' behavior that likely maps to the order parameter, but the phrasing is ambiguous rather than additive.

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 specific resource (every perpetual future across eight named venues) and a specific operation (a ranked screener with four sort keys), which is far more informative than the bare name. It implicitly separates itself from single-metric siblings like open_interest and perp_funding_rates by stressing 'in one call' across all venues, though it never names those siblings directly.

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 guidance on when to pick this over derivatives_snapshot, perp_funding_rates, or open_interest. The only conditional statements are billing rules ('Bad input is free; under 3 venues not charged. Empty filter results are still charged'), which tell the agent about cost, not about tool selection.

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.