Skip to main content
Glama

EmblemAI AgentWallet

nansen-perps: nansen_perp_screener

nansen_perp_screener
Read-onlyIdempotent

Screen Hyperliquid perp markets over a window: volume, buy/sell pressure, open interest, funding (incl. annualized), trader count, price change. With trader_type 'sm' it measures Smart Money volume, net position change and Smart Money longs/shorts. 1 credit.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days ending now (default 1). Ignored when date_from is set.
pageNoPage number for pagination (default 1)
limitNoRows to return (1-100, default 20)
date_toNoExplicit end (YYYY-MM-DD or ISO 8601). Defaults to now.
sort_byNoSort field. 'smart_money_*' fields need trader_type 'sm'; 'buy_volume/sell_volume/buy_sell_pressure' need 'all'; 'current_position_*' need whale/public_figure. Default: smart_money_volume for sm, volume otherwise.
date_fromNoExplicit start (YYYY-MM-DD or ISO 8601). Overrides days.
trader_typeNoWhose activity to measure (default all)
token_symbolNoOnly this coin
sort_directionNoSort direction (default DESC)
include_price_changeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds a genuinely non-structured behavioral fact: the call costs 1 credit, which matters for an agent planning repeated screening calls. It does not describe return shape, row ordering defaults, or pagination limits beyond what the schema already states, which keeps it from 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.

Conciseness5/5

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

Two sentences, front-loaded with the resource and window, then the metric list, then the mode caveat and cost. Every clause carries information; nothing is boilerplate or restated from the title.

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 10 optional parameters and no output schema, the definition compensates by naming the metric columns, which effectively previews the returned fields. Pagination and date semantics are handled by the schema, and safety by annotations, so an agent has enough to call it correctly. It only lacks a clear statement of what a row represents (coin-level aggregation) versus sibling tools.

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 90%, so the schema already documents days, date_from/date_to, pagination, sort_by and trader_type in detail. The description adds only high-level meaning (which metrics are measured, what 'sm' changes, that funding is annualized) rather than syntax or default behavior. This lands at the baseline for a well-documented schema.

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?

States a specific verb and resource ('Screen Hyperliquid perp markets over a window') and enumerates the metrics produced (volume, buy/sell pressure, open interest, funding incl. annualized, trader count, price change). It also explains the 'sm' mode shift, so an agent can tell it apart from trade-level or position-level siblings. It stops short of explicitly naming which sibling to use for wallet-level or leaderboard needs.

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: it is the market-wide ranking/screening tool over a time window, and the trader_type note hints at when the smart-money variant applies. However, there is no explicit when-to-use versus nansen_perp_positions, nansen_perp_leaderboard or nansen_perp_trades, and no stated prerequisites or exclusions. Adequate but reliant on the agent inferring the screening role from the name and metric list.

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