Skip to main content
Glama

EmblemAI AgentWallet

nansen-perps: nansen_wallet_perp_pnl

nansen_wallet_perp_pnl
Read-onlyIdempotent

Hyperliquid PnL scorecard for one wallet over a window: realized PnL and %, win rate, closed/winning trade counts, fees, and top 5 coins by PnL. 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": {
      "wallet_address": "<wallet_address>"
    },
    "name": "nansen_wallet_perp_pnl"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days ending now (default 30). Ignored when date_from is set.
date_toNoExplicit end (YYYY-MM-DD or ISO 8601). Defaults to now.
date_fromNoExplicit start (YYYY-MM-DD or ISO 8601). Overrides days.
wallet_addressYesHyperliquid (EVM-format) address

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 cover the safety profile (readOnly, idempotent, non-destructive, open world), so the description's added value is the concrete return contents and the '1 credit' cost disclosure, which matters for tool budgeting. With no output schema present, naming the returned fields is genuinely useful behavioral context; only scope limits (e.g. Hyperliquid-only, closed-trade-only counting) are left implicit.

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 what the tool is and what it returns, ending with the credit cost. Every clause carries information; nothing is redundant with the schema.

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 read-only analytics call with no output schema, the description enumerates the metrics an agent should expect back and the cost, which is enough to decide whether to call it. Minor gaps remain around whether metrics are limited to closed trades and how the window interacts with the perp-only scope.

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 100%, so days/date_from/date_to/wallet_address are already fully documented, including the days-overridden-by-date_from rule. The description's 'over a window' adds only framing, not syntax or precedence detail beyond the schema, so baseline 3 applies.

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: a Hyperliquid PnL scorecard for one wallet over a window, and enumerates the metrics returned (realized PnL and %, win rate, closed/winning counts, fees, top 5 coins). It is clearly distinguishable from position/trade-list siblings by being a scorecard, though it never names an alternative tool explicitly.

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 rather than stated: the phrase 'for one wallet over a window' tells the agent this is a single-wallet performance summary and the window parameters apply, but there is no explicit when-to-use or when-not-to-use guidance versus nansen_wallet_pnl or the perp position/trade 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