Skip to main content
Glama
Sign In

AlphaYou: Smart Money Intel

by net.alphayou
OverviewDiscussionsAdmin

Research a public wallet

analyze_hyperliquid_wallet
Read-only

Use for historical performance and risk of a supplied public Hyperliquid address. Cached metrics and available history only, not live positions or owner identity.

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": {
      "address": "<address>"
    },
    "name": "analyze_hyperliquid_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesPublic wallet address, 0x plus 40 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / address / description
      Added value: +"Public wallet address, 0x plus 40 characters"
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly and non-destructive, so the bar is lower. The description still earns credit for disclosing that results come from cached metrics and available history only, which warns the agent about data staleness and incomplete coverage.

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?

Two tight sentences, with the use case front-loaded and the negative scoping second; nothing is wasted. Wording like "supplied" is slightly redundant but not costly.

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 no output schema, the description does the necessary work of setting expectations: cached historical metrics rather than live state. A brief hint at what a "risk" metric includes would close the remaining gap, but the agent has enough to call it 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?

Only one parameter, and the schema already has 100% description coverage including a 0x address pattern. The description's "supplied public Hyperliquid address" adds the public-vs-private nuance but no format or validation detail beyond the schema.

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-plus-resource ("historical performance and risk of a supplied public Hyperliquid address") and immediately scopes what it is not (live positions, owner identity), which cleanly separates it from the sibling get_hyperliquid_wallet_positions.

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?

Explicitly says when to use it (historical performance/risk) and when not to (live positions, owner identity), which is well above typical guidance. It stops short of naming the alternative sibling tool, so the agent must infer the redirect from the exclusion.

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 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