Skip to main content
Glama

Aevum: verified trading records

Check a Hyperliquid wallet

check_hyperliquid_wallet
Read-only

A Hyperliquid wallet's highlight vs its whole record, from Hyperliquid's own public data: this week / 30 days / all-time P&L, how it did before this month, max drawdown, account value, and stats over recent closed trades (win rate, average win vs loss, worst trade). Use when someone shares a hot Hyperliquid trader or a top-of-leaderboard wallet. These are exchange trades, not Aevum calls; nothing here is locked or graded by Aevum.

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": {
      "address": "<address>"
    },
    "name": "check_hyperliquid_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesHyperliquid wallet address, 0x + 40 hex

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuine context beyond that by naming the data source (Hyperliquid's own public data) and clarifying these are exchange trades rather than Aevum-graded records. It does not cover behavior for a non-Hyperliquid or malformed address, or freshness/rate-limit characteristics.

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?

Two sentences, front-loaded with the returned metrics and followed by the usage trigger and scope caveat; no filler. The first sentence is dense and the 'highlight vs its whole record' framing is slightly abstract compared to the plain metric list that follows it.

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 no output schema, the description usefully compensates by itemizing the metrics returned, and the single-parameter shape is fully covered by the schema. The remaining gap is error/edge behavior for addresses that are not Hyperliquid wallets, which matters for an open-world lookup.

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% with a single required 'address' documented as 0x + 40 hex, so the schema does the heavy lifting and the baseline applies. The description only marginally adds meaning by implying the address must be a Hyperliquid wallet specifically, without format or validation detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (a Hyperliquid wallet) and enumerates exactly what is returned: this-week/30-day/all-time P&L, pre-this-month performance, max drawdown, account value, and closed-trade stats. The chain qualifier ('Hyperliquid') is enough to separate it from check_polymarket_wallet and check_payout_wallet without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use when someone shares a hot Hyperliquid trader or a top-of-leaderboard wallet' gives a concrete triggering scenario, and the closing line implicitly excludes Aevum-scoped data ('not Aevum calls; nothing here is locked or graded by Aevum'). It stops short of naming the sibling to use instead for on-chain/Aevum records, so the exclusion is stated but not routed.

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