Skip to main content
Glama

Tape — Hyperliquid Analytics

Hyperliquid Wallet Risk Report

tape_wallet_analysis
Read-onlyIdempotent

Risk and track-record report for one public Hyperliquid wallet: equity, open positions, effective leverage, distance to liquidation, and history. Gemini is $0.01 per call (included while a Pro or Desk pass is active). voice=grok is $0.10 per call. Billing period is per call. Per-call tools do not renew. Stop calling to cancel. Use after tape_leaderboard or tape_whale_prints hands you an address. Read-only public chain data; informational only. For educational purposes only. Not trading advice. Not investment advice. Independent. Not affiliated with Hyperliquid Labs or the Hyperliquid Foundation.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "voice": "gemini",
      "address": "0x0000000000000000000000000000000000000000"
    },
    "name": "tape_wallet_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
voiceNogemini is $0.01 per call. grok is $0.10 per call.
addressYesWallet address: 0x followed by exactly 40 hex characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "address": "0x0000000000000000000000000000000000000000",
      +    "voice": "gemini"
      +  }
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / voice / description
      Previous value: -"AI voice. Gemini is included with Pro. Grok and Claude are metered second voices."New value: +"gemini is $0.01 per call. grok is $0.10 per call."
    • changedInput schema / properties / voice / enum
      Previous value: -[
      -  "gemini",
      -  "grok",
      -  "claude"
      -]New value: +[
      +  "gemini",
      +  "grok"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / voice / description
      Previous value: -"AI voice. Gemini is included with Pro. Grok is a metered second voice."New value: +"AI voice. Gemini is included with Pro. Grok and Claude are metered second voices."
    • changedInput schema / properties / voice / enum
      Previous value: -[
      -  "gemini",
      -  "grok"
      -]New value: +[
      +  "gemini",
      +  "grok",
      +  "claude"
      +]
  4. Changed2 schema fields changed
    • changedInput schema / properties / voice / description
      Previous value: -"AI voice. Gemini is included with Pro. Grok and Claude are metered second voices."New value: +"AI voice. Gemini is included with Pro. Grok is a metered second voice."
    • changedInput schema / properties / voice / enum
      Previous value: -[
      -  "gemini",
      -  "grok",
      -  "claude"
      -]New value: +[
      +  "gemini",
      +  "grok"
      +]
  5. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive behavior, so the safety profile is covered. The description adds genuinely new behavioral context: the exact billing model ($0.01 Gemini, $0.10 grok, per call, non-renewing, cancel by ceasing calls), the data provenance ('read-only public chain data'), and the informational-only framing. Cost and billing semantics are decision-critical for an agent and appear nowhere in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is correctly front-loaded, but the body degrades into a run-on of billing clauses ('Billing period is per call. Per-call tools do not renew. Stop calling to cancel.') followed by four overlapping legal disclaimers ('For educational purposes only. Not trading advice. Not investment advice...'). Several sentences restate cost information the schema already carries.

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?

With no output schema, the description compensates by naming the report's contents (equity, positions, leverage, liquidation distance, history). Safety, cost, provenance, upstream sequencing, and return shape are all covered, which is everything an agent needs to invoke this 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%, so the baseline is 3. The description repeats the voice pricing already documented in the schema's voice property and never explains what 'voice' actually selects (the report-generating engine) versus the address parameter, adding little semantic meaning beyond the structured fields.

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?

Opens with a specific verb plus resource ('Risk and track-record report for one public Hyperliquid wallet') and enumerates the exact contents: equity, open positions, effective leverage, distance to liquidation, and history. An agent can distinguish this from tape_leaderboard or tape_whale_prints without opening either 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?

States clear upstream context: 'Use after tape_leaderboard or tape_whale_prints hands you an address,' which tells the agent when this tool belongs in a workflow. It gives no explicit exclusions (e.g., when a plain balance lookup or a market-wide tool would be preferable instead), so it falls short of full when/when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources