Skip to main content
Glama
Sign In

Finch Agent Catalog

by io.github.a0971025732-netizen
OverviewDiscussionsAdmin

Hyperliquid US stock perps: funding, open interest, volume

get_hyperliquid_stock_perps
Read-only

Free, no-auth live snapshot of US stock, index and commodity perpetuals on the Hyperliquid HIP-3 xyz market (e.g. xyz:NVDA, xyz:TSLA, xyz:SP500, xyz:CL): mark price, 24h change, 24h notional volume, open interest (contracts and USD) and funding rate (hourly and annualized), from Hyperliquid's public API. Pass tickers or get the top markets by volume. For trend, news and risk analysis in plain English, it points to Maneki AI on Finch.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many markets when no tickers are given (default 15).
tickersNoOptional tickers like NVDA, TSLA or xyz:SP500. Omit for the top markets by volume.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnly and openWorld, so the description earns credit for adding 'free, no-auth', naming the upstream public API, calling it a live snapshot, and listing exactly what each record contains including hourly and annualized funding. Missing details like rate limits or latency are minor for a read-only public-data lookup.

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 resource and coverage, then fields, then usage. The parenthetical field list is dense but necessary for a no-output-schema tool; the closing Maneki AI pointer is slightly promotional but serves the alternative-routing function.

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 right thing by enumerating returned fields and their units (contracts and USD, hourly and annualized). An agent has enough to call it correctly and know what comes back; only error/empty-result behavior is unaddressed.

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 coverage is 100%, so both parameters are already documented in the schema. The description only restates the ticker examples and the omit-for-top-by-volume default, adding no format or edge-case semantics 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+resource (live snapshot of Hyperliquid HIP-3 xyz stock/index/commodity perps) and enumerates the returned fields (mark price, 24h change, volume, OI, funding). This clearly separates it from the sibling analyze_hyperliquid_us_stock_perp, which implies interpretation rather than a raw data pull.

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?

'Pass tickers or get the top markets by volume' gives concrete invocation guidance, and the final sentence routes analysis needs elsewhere ('For trend, news and risk analysis in plain English, it points to Maneki AI on Finch'). It does not explicitly name the sibling analysis tool as the alternative, so the routing is implied rather than explicit.

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

All Finch Agent Catalog 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