Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

hyperliquid

Read-onlyIdempotent

Fetch perpetual futures context—hourly funding, open interest, mark/oracle/mid prices, premium and 24h volume—for a symbol to assess market conditions.

Instructions

[Trading Data API] Hyperliquid perpetual context: funding (hourly), open interest, mark/oracle/mid price, premium, 24h volume. Not geo-blocked.

Example: /v1/hyperliquid?symbol=BTC

Use when you need Hyperliquid perp context: funding, open interest, mark/oracle price, premium and volume. Not for Binance/Bybit aggregates (use funding_oi).

Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

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": {
      "symbol": "<symbol>"
    },
    "name": "hyperliquid"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesRequired. Hyperliquid coin name (e.g. BTC, ETH, SOL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.8/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 the description adds genuinely non-derivable behavior: x402 USDC-on-Base pricing or free with an API key, and that an HTTP 402 carries a decoded price quote in payment_required rather than being a failure. It also warns the endpoint is not geo-blocked, which no annotation conveys.

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 payload fields, then example, then usage routing, then behavior — a sensible order with no filler. The opening field list and the 'Use when you need...' sentence partially restate the same content, which is the only redundancy.

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?

For a single-parameter read tool with no output schema, the description covers return contents, auth/payment paths, the 402 edge case, and the sibling alternative. Nothing an agent needs to call it or interpret a non-200 response is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a described required symbol field, so the baseline is 3; the description adds a concrete invocation example (`/v1/hyperliquid?symbol=BTC`) and the coin-name convention (BTC, ETH, SOL) that reinforces the schema's intent. It stops short of any edge-case handling for invalid symbols.

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 the specific resource (Hyperliquid perpetual context) and enumerates exactly what it returns: hourly funding, open interest, mark/oracle/mid price, premium, 24h volume. It explicitly separates itself from the sibling funding_oi by naming it as the tool for Binance/Bybit aggregates, so an agent can discriminate without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use ('need Hyperliquid perp context') and an explicit when-not-to-use with the named alternative ('Not for Binance/Bybit aggregates (use funding_oi)'). This is the strongest form of routing guidance among the siblings.

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

Deploy Server

Other Tools