Skip to main content
Glama
romudille-bit

AgentPay x402 — Economic-intelligence layer for AI Agents

by romudille-bit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

funding_rates

Read-onlyIdempotent

Fetch perpetual futures funding rates across Binance, Bybit, and OKX to gauge leveraged sentiment or the cost of holding a perp position.

Instructions

Get perpetual futures funding rates across Binance, Bybit, and OKX

Use when: You need funding rates to gauge leveraged market sentiment or cost of holding a perp position. Not for: you need open interest or long/short ratio — open_interest; one verdict combining funding, OI, slippage and security for a trade — pre_trade_check. Returns: funding_rate_pct, annualized_rate_pct, sentiment (bullish/neutral/bearish) per exchange Example response: {"asset": "BTC", "rates": [{"exchange": "binance", "funding_rate_pct": 0.012, "annualized_rate_pct": 13.14, "sentiment": "bullish"}, {"exchange": "bybit", "funding_rate_pct": 0.011, "annualized_rate_pct": 12.04, "sentiment": "bullish"}, {"exchange": "okx", "funding_rate_pct": 0.009, "annualized_rate_pct": 9.85, "sentiment": "neutral"}], "source": "binance/bybit/okx"}

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'. Leave empty for all major assets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.2
    • addedInput schema / properties / asset / description
      Added value: +"Token symbol, e.g. 'BTC', 'ETH'. Leave empty for all major assets."
  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 already cover read-only/idempotent safety, and the description adds value beyond them: cost ('free'), auth requirements ('no API key, nothing signed or spent'), data provenance ('live public data'), and failure modes ('fails with an error message on an unknown symbol or an unreachable upstream source').

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?

Strongly front-loaded and sectioned (purpose, use when, not for, returns, example, cost). The 'Returns' field list and the JSON example overlap somewhat, costing a little efficiency, but both are defensible given 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 supplies the return shape (funding_rate_pct, annualized_rate_pct, sentiment per exchange) plus a concrete example and error behavior, and its annotations carry the safety profile. Nothing needed for correct invocation is missing.

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?

The single 'asset' parameter is already fully documented in the schema (100% coverage, including the empty-string-for-all-majors behavior). The description adds no format, casing, or lookup guidance beyond that, so it meets the baseline without extending it.

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+resource ('Get perpetual futures funding rates') and scopes it to three named exchanges, which immediately separates it from single-venue or generic market tools in the sibling list.

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?

Explicit 'Use when' clause names the decision context (gauging leveraged sentiment / cost of holding a perp), and the 'Not for' clause routes to two exact siblings (open_interest, pre_trade_check) with the conditions that select them.

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