Skip to main content
Glama
Sign In

AgentPay — trust routing + spend caps for x402 agents

by io.github.romudille-bit
OverviewDiscussionsAdmin

open_interest

Read-only

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,"oi_change_1h_pct":1.2,"oi_change_24h_pct":12.4,"long_short_ratio":1.08,"long_short_ratios":{"Binance":1.08,"OKX":1.11,"Gate.io":1.02},"long_short_spread":0.09,"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/okx + gate/bitget (L/S)","primary":"binance"}

Price: $0.000 USDC per call

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description focuses on added context: which exchanges feed the data ('binance/bybit/okx + gate/bitget'), primary source, per-exchange breakdown, and an interpretive rule ('rising OI with high funding = overcrowded position'). It omits freshness/latency and failure behavior when an asset has no perp market, keeping it below 5.

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 one-line purpose, then structured Use when / Not for / Returns / example blocks. Minor redundancy: the closing 'Combine with funding_rates for a full derivatives picture' restates the opening sentence, and the example JSON is long, though justified since there is no output schema.

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 fully by listing return fields (total_oi_usd, oi_change_1h_pct, oi_change_24h_pct, long_short_ratio, per-exchange breakdown) and a full sample response including the nested exchanges array. An agent knows the shape and interpretation of the result before calling.

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?

Only one parameter, and the schema description coverage is 100% ('Token symbol, e.g. BTC, ETH, SOL'), so the schema carries the semantics. The description adds nothing further about the asset argument beyond the example payload, which is the baseline case.

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 for any asset') plus the derived metrics returned. It explicitly names sibling tools (funding_rates, pre_trade_check) so the agent can distinguish it without opening the schema.

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' blocks, each routing to the correct alternative ('funding_rates' for funding cost, 'pre_trade_check' for a trade verdict). Both positive and negative selection criteria are present.

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

All AgentPay — trust routing + spend caps for x402 agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources