Skip to main content
Glama

Cross-Venue Perps Funding

perps_cross_venue_funding

Compare borrow/funding APR + OI across Solana on-chain venues (Jupiter Perps, Adrena, Flash, Phoenix) and cross-chain reference (Hyperliquid, dYdX v4). Returns best entry per side, basis vs Hyperliquid, and arbitrage opportunities. SOL/BTC/ETH/BONK supported (with venue-specific availability).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "market": "<market>"
    },
    "name": "perps_cross_venue_funding"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketYesAsset to query
include_referenceNoInclude Hyperliquid + dYdX v4 reference rates

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses the return payload (best entry per side, basis vs Hyperliquid, arbitrage opportunities) and a real behavioral caveat — venue-specific asset availability — which tells the agent results may be sparse for some markets. It stops short of stating read-only safety, latency/freshness, or behavior when a venue is unreachable, which matters for a multi-source aggregator.

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?

Three tight sentences with no filler: the comparison scope comes first, then the returned artifacts, then supported assets and the availability caveat. Every clause carries information the agent needs.

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 and no annotations, the definition still conveys what is compared, which venues are included, what the result contains, and which assets are supported. It is close to complete for a read-only aggregator; missing only data-freshness expectations and behavior on partial venue failure.

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 the baseline is 3, but the description adds genuine meaning: it names the reference venues behind include_reference (Hyperliquid and dYdX v4) and clarifies that availability of an asset varies by venue, which frames why the market enum can yield uneven results. That goes beyond 'Asset to query' and 'Include Hyperliquid + dYdX v4 reference rates'.

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 uses a specific verb and resource — compare funding/borrow APR plus OI — and enumerates the exact venue universe (Jupiter Perps, Adrena, Flash, Phoenix, plus Hyperliquid and dYdX v4). It is clearly distinguishable from generic siblings like query or compare_tokens, but it does not explicitly contrast itself with near-neighbors perps_venue_comparison, perps_basis_signal, or perps_market_structure, which is the main remaining ambiguity.

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 rather than stated: the mention of 'best entry per side' and 'arbitrage opportunities' signals this tool is for cross-venue funding/basis analysis, and the SOL/BTC/ETH/BONK note sets scope. However, there is no explicit when-to-use rule, no exclusion of the overlapping perps_* siblings, and no prerequisites or caveats about data freshness.

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.