Skip to main content
Glama

Antigravity x402 & MCP Gateway

fetch_crypto_derivatives_pulse

[0.005000 USDC via x402] Returns real-time Hyperliquid L1 perpetual mark/oracle basis (bps), hourly & annualized funding carry APY %, USD open interest, 24h volume, and Deribit 30-day BTC/ETH options implied volatility index (DVOL).

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

Input Schema

NameRequiredDescriptionDefault
symbolsNoList of perpetual ticker symbols to query (up to 12, default ['BTC','ETH','SOL','XRP','HYPE']).
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.005000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the key behavioral trait: this is a paid x402 endpoint costing 0.005000 USDC, with the chain options visible in the schema. It omits rate limits, caching/freshness guarantees for "real-time" data, and error behavior on unpaid or invalid signatures, keeping it short of a 5.

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?

One dense sentence with zero filler, and every clause names a distinct metric. The price tag being front-loaded ahead of the actual purpose is a minor mis-ordering, and the acronym-heavy phrasing (bps, APY, DVOL) requires domain literacy, but nothing is redundant.

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?

There is no output schema, so the description must enumerate return values, and it does so thoroughly: basis, funding carry, open interest, volume, and implied volatility. Combined with the cost and payment path in the schema, an agent has everything needed to decide, pay, and interpret results for this read-only data fetch.

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%, so both parameters are already documented, making the baseline 3. The description adds marginal meaning by tying the returned series to specific assets (BTC/ETH for DVOL) and framing the payment token, which helps the agent interpret the symbols list and the payment flow, though it does not explain symbol format or the cap of 12.

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?

The description gives a specific verb ("Returns") plus a precisely enumerated resource: Hyperliquid L1 perpetual mark/oracle basis in bps, hourly and annualized funding APY, USD open interest, 24h volume, and Deribit 30-day BTC/ETH DVOL. An agent can tell exactly what data arrives, and none of the siblings return derivatives market data, so the tool is unambiguous in context.

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

Usage Guidelines3/5

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

Usage is implied by the content (crypto perp/funding/volatility data), but there is no explicit when-to-use or when-not-to-use guidance, and no pointer to a related sibling such as list_x402_pricing_and_wallets for pricing details. The embedded price tag hints at the paid-access workflow but does not spell out the sequence of calling without a signature to obtain a quote.

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.