AlphaYou: Smart Money Intel

Find Hyperliquid traders

search_hyperliquid_traders

Read-only

Use for a historical score or Sharpe ranking of the qualified trader cohort. Returns at most ten rows per page, with next_offset when more are available. Accepts an optional exact asset and leverage-tier filter. Not a market-wide ranking, 30-day PnL sort or personalized recommendation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_hyperliquid_traders"
  }
}

Input Schema

Name	Required	Description	Default
`asset`	No	Exact market symbol, like BTC or xyz:NVDA
`limit`	No	Rows per page, 1 to 10
`offset`	No	Rows to skip, 0 to 10,000
`sort_by`	No	Rank by trader score or Sharpe	trader_score
`leverage_tier`	No	Only traders in this leverage tier

Output Schema

Name	Required	Description	Default
`kind`	Yes
`traders`	Yes
`next_offset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 13, 2026

changedInput schema / properties / offset / description

Previous value: -"Rows to skip; use next_offset for the next page"New value: +"Rows to skip, 0 to 10,000"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "kind": {
+      "const": "discovery",
+      "type": "string"
+    },
+    "next_offset": {
+      "anyOf": [
+        {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "traders": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "address": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "address"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "kind",
+    "traders",
+    "next_offset"
+  ],
+  "type": "object"
+}

Changed5 schema fields changedNov 12, 2026
- addedInput schema / properties / asset / description
```
Added value: +"Exact market symbol, like BTC or xyz:NVDA"
```
- addedInput schema / properties / leverage_tier / description
```
Added value: +"Only traders in this leverage tier"
```
- addedInput schema / properties / limit / description
```
Added value: +"Rows per page, 1 to 10"
```
- addedInput schema / properties / offset / description
```
Added value: +"Rows to skip; use next_offset for the next page"
```
- addedInput schema / properties / sort_by / description
```
Added value: +"Rank by trader score or Sharpe"
```
First observedOct 11, 2026

TDQS

A4.2/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 and the description is not contradicting them. It adds real behavioral detail beyond that: a hard cap of ten rows per page and a next_offset cursor when more results exist, plus the fact that filters are optional. It stops short of stating whether the ranking is snapshot or point-in-time, or whether the cursor expires.

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?

Four short sentences, front-loaded with the primary use case, then output shape, then parameter behavior, then exclusions. Every sentence carries distinct information and none is a restatement of the name or annotations.

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 an output schema present and full schema coverage, the description need not explain return fields, and it correctly focuses on scope, pagination and exclusions. The one unresolved term is 'qualified trader cohort' — the description never says what qualification means, which matters because the cohort boundary defines who can appear in results.

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 the schema already documents all five parameters including the enum values and ranges, and the baseline of 3 applies. The description reinforces the 'exact asset' and 'leverage-tier' semantics and links the sort_by choice to the ranking purpose, but adds no syntax or defaulting detail the schema lacks.

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?

The description names a specific verb-and-resource pairing (a historical score or Sharpe ranking of the qualified trader cohort) rather than restating the tool name. The closing sentence enumerates what it is not (market-wide ranking, 30-day PnL sort, personalized recommendation), which lets an agent separate it from siblings such as compare_hyperliquid_traders without opening any 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?

There is a clear 'Use for...' trigger plus explicit exclusions, so both the when and the when-not are stated. What is missing is a named alternative: the description tells the agent what this tool is not, but not which sibling to route to instead (e.g. for the excluded PnL sort or market-wide view).

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?