address_perp_positionsGet a wallet's Hyperliquid positions and liquidation risk without a portfolio lookup.
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes | Complete request for a wallet's open Hyperliquid perpetual positions. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / request / additionalPropertiesAdded value: +falseInput schema / properties / request / properties / filters / anyOfPrevious value: -[
- {
- "additionalProperties": false,
- "description": "Filters for a wallet's open Hyperliquid perpetual positions.",
- "properties": {
- "positionType": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Filter by position type, such as oneWay."
- },
- "positionValueUsd": {
- "anyOf": [
- {
- "description": "Numeric range where from_value and to_value are optional,\nallowing for open-ended ranges (e.g., only minimum or only maximum).",
- "properties": {
- "from": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Minimum value (inclusive), optional"
- },
- "to": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Maximum value (inclusive), optional"
- }
- },
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Filter by absolute position value in USD."
- },
- "tokenSymbol": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Filter by a Hyperliquid perp symbol, such as BTC or HYPE."
- },
- "unrealizedPnlUsd": {
- "anyOf": [
- {
- "description": "Numeric range where from_value and to_value are optional,\nallowing for open-ended ranges (e.g., only minimum or only maximum).",
- "properties": {
- "from": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Minimum value (inclusive), optional"
- },
- "to": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Maximum value (inclusive), optional"
- }
- },
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Filter by unrealized profit or loss in USD."
- }
- },
- "type": "object"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "description": "Filters for a wallet's open Hyperliquid perpetual positions.",
+ "properties": {
+ "positionType": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Filter by position type, such as oneWay."
+ },
+ "positionValueUsd": {
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "description": "Numeric range where from_value and to_value are optional,\nallowing for open-ended ranges (e.g., only minimum or only maximum).",
+ "properties": {
+ "from": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Minimum value (inclusive), optional"
+ },
+ "to": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Maximum value (inclusive), optional"
+ }
+ },
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Filter by absolute position value in USD."
+ },
+ "tokenSymbol": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Filter by a Hyperliquid perp symbol, such as BTC or HYPE."
+ },
+ "unrealizedPnlUsd": {
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "description": "Numeric range where from_value and to_value are optional,\nallowing for open-ended ranges (e.g., only minimum or only maximum).",
+ "properties": {
+ "from": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Minimum value (inclusive), optional"
+ },
+ "to": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Maximum value (inclusive), optional"
+ }
+ },
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Filter by unrealized profit or loss in USD."
+ }
+ },
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / request / properties / orderBy / anyOfPrevious value: -[
- {
- "items": {
- "description": "One sort rule for a wallet's open Hyperliquid perpetual positions.",
- "properties": {
- "direction": {
- "description": "Sort direction. Use DESC for the largest values first.",
- "enum": [
- "ASC",
- "DESC",
- "asc",
- "desc"
- ],
- "type": "string"
- },
- "field": {
- "description": "Position field to sort by.",
- "enum": [
- "leverage_value",
- "position_value_usd",
- "entry_price_usd",
- "liquidation_price_usd",
- "unrealized_pnl_usd",
- "size",
- "token_symbol",
- "position_type"
- ],
- "type": "string"
- }
- },
- "required": [
- "field",
- "direction"
- ],
- "type": "object"
- },
- "type": "array"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "items": {
+ "additionalProperties": false,
+ "description": "One sort rule for a wallet's open Hyperliquid perpetual positions.",
+ "properties": {
+ "direction": {
+ "description": "Sort direction. Use DESC for the largest values first.",
+ "enum": [
+ "ASC",
+ "DESC",
+ "asc",
+ "desc"
+ ],
+ "type": "string"
+ },
+ "field": {
+ "description": "Position field to sort by.",
+ "enum": [
+ "leverage_value",
+ "position_value_usd",
+ "entry_price_usd",
+ "liquidation_price_usd",
+ "unrealized_pnl_usd",
+ "size",
+ "token_symbol",
+ "position_type"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "field",
+ "direction"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that liquidation risk is returned and that no separate portfolio call is needed, but says nothing about whether only open positions are included, how liquidation risk is derived, or any limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler. It is efficient, though arguably terse for a tool with nested filter and sort structures.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema, rich annotations and full schema coverage, the description only needs to establish purpose and routing, which it does. The one gap is that it never hints the tool supports filtering and sorting, which an agent might otherwise miss.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the nested request object documents address, filters (tokenSymbol, positionType, value/PnL ranges) and orderBy in detail. The description contributes nothing about these parameters, so it neither compensates nor detracts — baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb + resource: it returns a wallet's Hyperliquid perpetual positions plus liquidation risk. The phrase 'without a portfolio lookup' implicitly contrasts it with the heavier address_portfolio sibling, though that sibling is never named explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The clause 'without a portfolio lookup' hints that this is the lightweight path when the full portfolio isn't needed, which is useful implied guidance. There is no explicit when-to-use/when-not statement and no named alternative for cases where portfolio context is required.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.