Skip to main content
Glama

EmblemAI AgentWallet

nansen-perps: nansen_position_intelligence

nansen_position_intelligence
Read-onlyIdempotent

One-shot long vs short summary for a Hyperliquid coin: total USD long, short and gross for Smart Traders, whales and public figures. Fastest way to read positioning sentiment. 1 credit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token_symbol": "<token_symbol>"
    },
    "name": "nansen_position_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
token_symbolYesHyperliquid coin symbol, e.g. 'BTC', 'ETH', 'SOL', 'HYPE'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive behavior, so the description only needs to add cost and scope. It does add the cost signal ("1 credit") and states the aggregation buckets, but says nothing about freshness, chains covered, or whether the figures are cumulative or current positions.

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?

Three short sentences: what it returns, who is covered, why to pick it, and the cost. Every clause carries information and the payoff statement is front-loaded with no filler.

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?

For a single-parameter read-only summary tool with no output schema, the description adequately conveys the returned dimensions (long, short, gross USD) and the credit cost. A brief note on data freshness or how the trader categories are defined would close the remaining gap.

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?

Only one parameter at 100% schema coverage, and the schema already describes the Hyperliquid coin symbol with examples. The description reinforces that the input is a Hyperliquid coin and that output is aggregated long/short/gross, but adds no format or constraint detail beyond the 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 concrete verb and resource: a one-shot long vs short USD summary for a Hyperliquid coin, broken out by Smart Traders, whales and public figures. The scope (single coin, aggregate positioning) is clear enough to separate it from list-style siblings, though it never names a specific alternative tool.

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?

"Fastest way to read positioning sentiment" implies a usage context and hints at cheaper/lighter alternatives, but gives no explicit when-not guidance, no prerequisites, and no named sibling to route to for per-trader detail.

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