AlphaYou: Smart Money Intel

Inspect multiple wallets

get_hyperliquid_wallets_positions

Read-only

Use for positions of two to five wallets in one batch call, for example after a ranking. Covers one venue with bounded upstream concurrency and reports individual wallet failures. Accepts an optional asset for named markets.

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": {
      "addresses": "<addresses>"
    },
    "name": "get_hyperliquid_wallets_positions"
  }
}

Input Schema

Name	Required	Description
`dex`	No	Venue prefix; empty for the main perp venue
`asset`	No	Market name, like Nvidia, BTC or NVDA
`addresses`	Yes	Two to five distinct wallet addresses

Output Schema

Name	Required	Description	Default
`kind`	Yes
`wallets`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "kind": {
+      "const": "positions_batch",
+      "type": "string"
+    },
+    "wallets": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "address": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "kind",
+    "wallets"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedNov 12, 2026
- addedInput schema / properties / addresses / description
```
Added value: +"Two to five distinct wallet addresses"
```
- addedInput schema / properties / addresses / items / description
```
Added value: +"Public wallet address, 0x plus 40 characters"
```
- addedInput schema / properties / asset / description
```
Added value: +"Market name, like Nvidia, BTC or NVDA"
```
- addedInput schema / properties / dex / description
```
Added value: +"Venue prefix; empty for the main perp venue"
```
First observedOct 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely new behavior: one venue per call, bounded upstream concurrency, and per-wallet failure reporting in a batch — the last being important for interpreting partial results.

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, front-loaded with the primary use case, then scope constraints, then the optional parameter. Every clause carries information and nothing is repeated from the schema verbatim.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The description completes the picture with batch size, venue scope, and partial-failure behavior; only edge cases such as invalid addresses or rate limits are left unaddressed.

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 the baseline is 3. The description still adds meaning by framing 'dex' as a single venue per call ('Covers one venue') and clarifying that 'asset' targets named markets, which explains how these two optional params interact.

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 (positions of multiple wallets) plus the batch scope of two to five wallets, which implicitly separates it from the singular get_hyperliquid_wallet_positions sibling. It never names the single-wallet alternative, so the differentiation is inferable rather than explicit.

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?

Gives a clear when-to-use signal: batch lookups of two to five wallets, with a motivating workflow ('for example after a ranking'). It does not state exclusions (e.g., use the singular tool for one wallet) or name an alternative, so it stops short of full routing guidance.

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

All AlphaYou: Smart Money Intel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?