Skip to main content
Glama
Sign In
hydromancer-mcp

hydromancer-mcp

by joshavenue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Wallet overview: balance, open positions, PnL record

hydromancer_wallet_overview
Read-only

Get a Hyperliquid wallet profile in one call: account value, open perpetual positions with PnL and liquidation prices, spot balances, and realized trading performance.

Instructions

One-call profile of any Hyperliquid wallet: account value, every open perp position (side, size, entry, liquidation price, leverage, unrealized PnL), spot balances and its realized trading record (PnL, win rate, trade count, volume, human score). Use this first for questions like "what is this wallet holding?" or "is this trader any good?". Set includeHip3=true to include HIP-3 markets such as xyz:TSLA.

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

Input Schema

NameRequiredDescriptionDefault
addressYesWallet address, 0x followed by 40 hex characters.
includeHip3NoAlso include positions on HIP-3 markets (stocks, indices, commodities). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so safety is covered. The description adds behavior beyond annotations: the concrete payload shape returned, and that HIP-3 markets are excluded by default and require includeHip3=true, which is a real scoping behavior an agent must know.

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 sentences, front-loaded with the core capability, then usage routing, then the opt-in flag. The dense parenthetical field list earns its space because there is no output schema to describe the return shape.

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 correctly takes on the burden of describing return contents and does so thoroughly. It omits edge behavior (invalid or empty wallets, response size for wallets with many positions), which matters somewhat given openWorldHint=true and no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are documented in the schema and the baseline is 3. The description goes slightly beyond by naming a concrete HIP-3 market example ('xyz:TSLA'), which clarifies the flag's practical scope beyond the schema's 'stocks, indices, commodities' phrasing.

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?

States a specific verb+resource ('One-call profile of any Hyperliquid wallet') and then enumerates exactly what the profile contains (account value, perp positions with side/size/entry/liq/leverage/uPnL, spot balances, realized record). This clearly separates it from hydromancer_wallet_trades and hydromancer_wallet_closed_trades, which cover trade lists rather than a consolidated snapshot.

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 this first for questions like "what is this wallet holding?" or "is this trader any good?"' gives concrete entry-point guidance with example user intents. It does not explicitly exclude or redirect to specific siblings (e.g., use wallet_trades for individual fills), so it stops short of full when/when-not routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools