Skip to main content
Glama
romudille-bit

AgentPay x402 — Economic-intelligence layer for AI Agents

by romudille-bit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

open_interest

Read-onlyIdempotent

Retrieve total open interest in perpetual futures for any asset, including 1h and 24h change rates. Pair with funding rates to detect overcrowded positions.

Instructions

Get total open interest in perpetual futures for any asset, with 1h and 24h change rates. Pairs with funding_rates to complete the derivatives picture — rising OI with high funding = overcrowded position.

Use when: You need to know total open interest in perpetual futures and whether it's rising or falling. Combine with funding_rates for a full derivatives picture. Not for: you need the funding cost of holding a position — funding_rates; a single trade verdict — pre_trade_check. Returns: total_oi_usd, oi_change_1h_pct, oi_change_24h_pct, long_short_ratio, per-exchange breakdown Example response: {"asset": "ETH", "price_usd": 2069.73, "total_oi_usd": 8420000000.0, "oi_change_1h_pct": 1.2, "oi_change_24h_pct": 12.4, "long_short_ratio": 1.08, "exchanges": [{"exchange": "Binance", "oi_contracts": 4066123.5, "oi_change_1h_pct": 1.2, "oi_change_24h_pct": 12.4, "long_short_ratio": 1.08}], "source": "binance/bybit"}

Price: free. Read-only live public data; no API key, nothing signed or spent. Fails with an error message on an unknown symbol or an unreachable upstream source.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetNoToken symbol, e.g. 'BTC', 'ETH', 'SOL'BTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.2
    • addedInput schema / properties / asset
      Added value: +{
+  "default": "BTC",
+  "description": "Token symbol, e.g. 'BTC', 'ETH', 'SOL'",
+  "type": "string"
+}
    • removedInput schema / properties / symbol
      Removed value: -{
-  "description": "Asset symbol, e.g. BTC or ETH",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "symbol"
-]
  2. Addedv0.3.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive, idempotent, openWorld), and the description adds genuinely new context: cost ('free'), no API key, nothing signed or spent, and the specific failure mode (error on unknown symbol or unreachable upstream). That is real disclosure beyond structured fields.

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?

Front-loaded with the core purpose and structured with clear labeled sections (Use when / Not for / Returns), which is efficient. However the example response is lengthy and the opening sentence's phrasing is partially repeated in the 'Use when' block, so it is slightly padded rather than maximally tight.

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?

With no output schema, the description compensates by enumerating return fields (total_oi_usd, oi_change_1h_pct, oi_change_24h_pct, long_short_ratio, per-exchange breakdown) and giving a concrete example response. Combined with usage routing and failure modes, an agent has everything needed to call it correctly.

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 coverage is 100% and there is a single optional parameter with a default of 'BTC', already fully documented in the schema. The description adds no syntax or format detail for the asset parameter, so the baseline of 3 applies.

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

Purpose5/5

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

States a specific verb and resource (get total open interest in perpetual futures) plus supplementary fields (1h/24h change rates). It explicitly distinguishes itself from siblings funding_rates and pre_trade_check by naming what each is for, so an agent can separate them without opening schemas.

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

Usage Guidelines5/5

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

Provides explicit 'Use when' and 'Not for' sections that name the alternative tools (funding_rates, pre_trade_check) and the conditions selecting each. It even articulates the combination pattern (rising OI + high funding = overcrowded), leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools