Skip to main content
Glama

Agent Exchange store

perps_funding

$0.002 via x402: Funding rates for all perps: current Hyperliquid funding, predicted funding on Hyperliquid, Binance and Bybit with next funding time, sorted by current funding; top and bottom extremes; filter coins=BTC,ETH or limit. Pay 0.002 USDC through https://store.agentexchange.work/gw/perps/funding?limit=20 Via the Agent Exchange store gateway; settled by Coinbase.

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

Input Schema

NameRequiredDescriptionDefault
coinsNocomma list to filter
limitNo1..300, default 50
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose the most important trait: this is a paid endpoint costing 0.002 USDC via x402, with the gateway URL and Coinbase settlement named. It stops short of describing pagination limits or error/402 behavior in prose, leaving that to the x_payment schema field.

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?

Purpose and price are front-loaded, which is good, but the single run-on sentence crams the payment flow, a sample URL with an embedded query string, and settlement details together, and the price is stated twice ('$0.002 via x402' and 'Pay 0.002 USDC'). The sample URL is also easily mistaken for the actual call format.

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 annotations and no output schema, the description adequately covers what is returned (funding rates across three venues, sorted, plus top/bottom extremes) and the payment requirement. Minor gaps remain around response shape and how the limit interacts with the 'top and bottom extremes' output, but the essential information for a correct call is present.

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 schema already documents coins, limit, and x_payment, establishing a baseline of 3. The description reinforces the filter usage with concrete examples (coins=BTC,ETH, limit=20) but adds no format or range detail beyond what the schema provides.

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 states a specific resource (funding rates for all perps) and enumerates exactly what it returns: current Hyperliquid funding, predicted Hyperliquid funding, plus Binance and Bybit rates with next funding time. This distinguishes it from siblings like perps_market and perps_mids without the agent needing to open any schema.

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 only implied: the agent can infer 'call this when you need funding rates,' and concrete filter examples (coins=BTC,ETH, limit) hint at usage. However, there is no explicit when-to-use or when-not guidance and no mention of the closely related perps_market/perps_mids siblings to route between them.

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