Skip to main content
Glama

AINDEX

Perps funding and open interest

get_derivatives
Read-only

Arcus' perps markets (what Arcus pTokens hold): funding rate, next funding, open interest, volume. With asset, its funding (per hour and a year), open interest and mark on Lighter RH, Lighter, Hyperliquid, Binance and Bybit, Binance's long/short ratios, the funding carry between venues, and liquidation clusters (from TrueNorth, labelled).

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

Input Schema

NameRequiredDescriptionDefault
assetNo
marketsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.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=true, so the safety profile is covered. The description earns credit for disclosing data provenance — live venue feeds (Lighter RH, Lighter, Hyperliquid, Binance, Bybit) plus an external vendor (TrueNorth) whose liquidation clusters are 'labelled' — which tells an agent the data is aggregated third-party rather than first-party. It does not mention freshness, rate limits, or what happens when an asset isn't listed on a venue.

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?

Two sentences with no filler, and the core scope ('Arcus' perps markets, what Arcus pTokens hold') is front-loaded. However, the second sentence is a long comma-chained list punctuated by awkward fragments ('With asset, its funding (per hour and a year)') that slow comprehension of what is otherwise a coherent field inventory.

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

Completeness3/5

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

With no output schema, the description usefully enumerates the returned fields and their sources, and it is a safe read-only tool so mutation semantics aren't needed. Gaps remain: zero required parameters means an unargumented call is possible, yet the description never says what that default returns, and the markets parameter is left undefined. These are notable for a two-parameter tool at 0% schema coverage.

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% for both parameters, so the description must carry the full burden. It partially explains asset by saying that supplying one returns funding per hour and per year, open interest and mark across the five venues, which adds real meaning. The markets array (up to 20 short alphanumeric strings) is never explained — it is ambiguous whether it filters venues or trading pairs — leaving a substantive gap.

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

Purpose3/5

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

The description enumerates the data the tool returns (funding rate, next funding, open interest, volume, mark, long/short ratios, funding carry, liquidation clusters) and names the venues, so the resource is identifiable. But it never states the action in a verb+resource form — it's a dense noun-phrase data catalog — and it doesn't explicitly contrast itself with siblings like get_spreads or get_candles that also cover market data. An agent can guess the purpose but must parse a run-on sentence to get there.

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 when-to-use guidance, no condition distinguishing a call with asset from a call without it, and no mention of when to use get_spreads or get_lighter_market instead. The only structural hint is the phrase 'With asset, ...', which implies a broader no-arg mode but doesn't state what that returns or when to prefer it.

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