Skip to main content
Glama
Sign In

Buildix: Hyperliquid Orderflow

by trade.buildix
OverviewDiscussionsAdmin

Top traders by Follow Score

get_top_traders
Read-onlyIdempotent

Returns the top 10 of the Buildix Top Traders ranking of large Hyperliquid accounts: address, label, Trader Score, confidence, style badge and, once the ranking exists, the official rank, Verified flag, Follow Score (what a follower copying 10 minutes late would have kept, adjusted for risk and sample size), follower PnL over 30 days and rank 24 hours ago. Wallets with a losing lifetime record, market makers and hedged books are not ranked. Position changes under $50,000 are not seen. Use it when the user asks which Hyperliquid wallets to study before copy trading. Data only: Buildix does not execute trades.

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

Input Schema

NameRequiredDescriptionDefault
detailNo"brief" (default) returns labels and key numbers. "full" adds the underlying values, data age and method notes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description adds substantial context beyond them: results are capped at 10, eligibility filters remove certain wallet classes, the $50,000 threshold explains omissions, ranking fields appear only 'once the ranking exists', and it explicitly states Buildix does not execute trades. That is unusually strong disclosure of what the agent will and will not see.

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?

Front-loaded with the core action and result shape, followed by eligibility caveats and a usage sentence. The middle field-list sentence is dense but every element is informative. A minor trim of the parenthetical Follow Score definition would sharpen it, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the burden of describing return values, and it does so field by field including the methodology behind Follow Score. Combined with the coverage-gap explanations and the no-execution disclaimer, an agent has everything needed to call and interpret this tool correctly.

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% and the single enum parameter 'detail' is fully documented in the schema itself. The description says nothing about brief versus full output, so it adds no meaning beyond the structured field. Baseline 3 applies where the schema carries the parameter semantics.

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 and resource (returns the top 10 of the Buildix Top Traders ranking of large Hyperliquid accounts) and enumerates the exact fields returned, including Trader Score, Follow Score, follower PnL and Verified flag. This is clearly distinguishable from the sibling tools, which cover funding, liquidations, screener, orderflow and whale positioning rather than wallet rankings.

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 an explicit trigger: 'Use it when the user asks which Hyperliquid wallets to study before copy trading.' It also lists exclusions that shape the result set (losing lifetime record, market makers, hedged books, sub-$50k position changes). It does not name a sibling alternative for related questions, 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 Buildix: Hyperliquid Orderflow toolsInspect
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