Skip to main content
Glama

Genexxis paid agent tools (x402)

perps_extremes

Highest and lowest annualized funding rates across all Binance USDT-margined perpetuals and Hyperliquid perps, with open interest in USD and a minimum open interest filter (default $5M). Price: $0.005 USDC per call, paid with x402 on Base.

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_extremes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows per side (1-50, default 10)
minOiUsdNoMinimum open interest in USD (default 5000000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the covered venues, the open interest filter default, and the pay-per-call price via x402 on Base, but it omits data freshness, rate limits, response shape, and error behavior.

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

Conciseness5/5

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

The description is two tight sentences, front-loading the purpose and scope before the pricing detail. Every sentence adds value without repetition or filler.

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?

For a simple two-parameter data tool with no annotations or output schema, the description covers purpose, venues, metric, filter default, and cost. It stops short of describing returned fields or freshness, which keeps it from being fully complete.

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 both parameters. The description repeats the minimum open interest default but adds no new meaning for the limit parameter or other invocation semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource and metric: highest and lowest annualized funding rates across specific Binance USDT-margined perpetuals and Hyperliquid perps, including open interest. It is specific enough to distinguish this as an extremes/ranking tool, but it does not explicitly name or contrast with sibling tools such as perps_funding or perps_oi.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no named alternatives are given. The scope implies cross-venue extremes, but an agent must infer when to choose this over perps_funding, perps_oi, or carry_ranking.

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