Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-perp-funding-arb

x402-perp-funding-arb: The same perpetual's funding on Polymarket Perps and Hyperliquid, both annualised to one basis, with the spread between them — a venue that charges less (or pays more) is the difference between a carry trade that works and one that bleeds.

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": "x402-perp-funding-arb"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
symbolNo
instrumentNo
minSpreadPctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / instrument / description
      Removed value: -"Instrument to process"
    • removedInput schema / properties / limit / description
      Removed value: -"Limit to process"
    • removedInput schema / properties / minSpreadPct / description
      Removed value: -"MinSpreadPct to process"
    • removedInput schema / properties / symbol / description
      Removed value: -"Symbol to process"
  2. First observed

TDQS

C2.6/5.0
Behavior2/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 it discloses almost nothing: no indication of whether it fetches live venue data, latency, rate limits, upstream failures, or how missing/illiquid markets are handled. The only behavioral hint is an implicit live two-venue fetch and the output shape (annualised rates plus spread), which is thin for a tool with zero annotation coverage.

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?

It is a single front-loaded sentence that states the comparison, but the closing clause about 'a carry trade that works and one that bleeds' is rhetorical padding that does not help invocation. The useful content is buried inside one long dash-separated sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Four undocumented parameters, no annotations, and no output schema mean the description should do much more than it does. It conveys the concept but leaves an agent unable to know how to parameterise the call or what the response contains.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, and the description never mentions limit, symbol, instrument, or minSpreadPct. Only indirect associations exist ('same perpetual' ↔ symbol/instrument, 'spread' ↔ minSpreadPct), and it does not explain why limit and minSpreadPct are typed as strings rather than numbers.

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 names the exact resource: the same perpetual's funding on Polymarket Perps and Hyperliquid, annualised, plus the spread between them. An agent can tell it computes a cross-venue funding comparison. It stops short of an explicit verb ('compute/compare/return') and never names nearby siblings such as x402-perp-funding-radar, x402-polyperp-funding, or x402-hyperliquid-funding, so the differentiation is left implicit.

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 statement of when to use this versus the many sibling funding tools, no prerequisites, and no exclusions. The carry-trade framing implies a use case but gives no selection rule an agent could apply.

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.