Skip to main content
Glama

Best funding arbitrage pairs

find_funding_arbs
Read-only

Delta-neutral funding pairs across the perp venues Angler trades: long where funding is lowest, short where it is highest, ranked by the spread's APR (before fees). Each can be run as a funding bot or by the funding autopilot on Angler's Bots page.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many pairs, 1-25. Default 10.
min_aprNoMinimum spread APR in percent. Default 10.
min_volume_usdNoMinimum 24h volume of the asset in USD (Binance, Hyperliquid and Lighter). Default 1,000,000; 0 includes thin and unlisted markets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description contributes real context beyond that: results are restricted to 'the perp venues Angler trades' (a closed universe, consistent with openWorldHint=false) and APR is quoted before fees. It does not describe the shape or cardinality of each pair record, so behavioral disclosure is useful but partial.

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?

Two sentences, front-loaded with the core mechanic and the ranking criterion, with the fee caveat parenthesized where it matters. The second sentence is the weakest - it is partly promotional ('Angler's Bots page') - but it still conveys an actionable next step, so it earns most of its space.

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

Completeness5/5

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

For a read-only, zero-required-parameter screening tool with no output schema and full schema coverage, the description supplies everything an agent needs to decide and call: the construction rule, the ranking metric, the fee caveat, and the venue universe. Returned fields are undocumented, but that gap is minor for a ranked screening query and does not affect correct invocation.

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, and the 'before fees' qualifier meaningfully disambiguates how min_apr should be read - it filters on gross spread APR, not net. The venue scope in the description also implicitly explains min_volume_usd's coverage (Binance, Hyperliquid, Lighter) before the schema spells it out. This is a small but genuine addition over the schema.

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 a specific resource (delta-neutral funding pairs) and defines the construction precisely: long the lowest-funding venue, short the highest, ranked by spread APR. That is far more informative than the title. It stops short of naming why it differs from siblings such as get_funding_rates or get_net_arbs (presumably net-of-fee), so the differentiation is only implicit in the 'before fees' parenthetical.

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?

The second sentence tells the agent what to do with results (run as a funding bot or via the funding autopilot), which implies downstream usage. However, there is no guidance on when to prefer this tool over get_funding_rates or get_net_arbs, and no note on when the default thresholds (10% APR, $1M volume) should be tightened or relaxed. Usage is suggested rather than scoped.

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