hyperliquid-whalealert-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COINGLASS_API_KEY | Yes | Your CoinGlass API key (required for API access) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_whale_alertsB | Fetch recent whale alerts and return as a Markdown table |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_whale_activity | Summarize recent whale activity |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as fetching whale alerts, making it distinct by default.
The single tool follows a clear verb_noun pattern (get_whale_alerts), which is consistent and predictable. Since there are no other tools to compare against, naming is inherently consistent.
A single tool is too few for the server's apparent purpose of monitoring whale alerts, as it lacks operations like filtering, subscribing, or historical queries. This minimal scope limits functionality and may cause agent failures due to incomplete coverage.
The tool surface is severely incomplete for a whale alert system, offering only fetching recent alerts without capabilities such as filtering by criteria, accessing historical data, or managing alerts. This creates significant gaps that will hinder agent workflows.