AgentFeed

Perp funding rate

get_funding_rate

Read-onlyIdempotent

Funding rate for any Hyperliquid perp: raw rate, interval hours, 8h equivalent, annualised rate, next funding time and mark price. Without a symbol, SOL and BTC from Hyperliquid with open interest. Costs 0.005 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	No	USDT perp symbol e.g. ETHUSDT, ONDOUSDT (omit for SOL and BTC from Hyperliquid)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	the get_funding_rate payload (without symbol: {sol, btc} from Hyperliquid; with symbol: {symbol, venues: {hyperliquid}}); a real captured example is free at https://x402.ochinimus.app/api/sample/get_funding_rate
`tool`	Yes	the tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026

changedOutput schema / properties / data / description

Previous value: -"the get_funding_rate payload (without symbol: {sol, btc} from Hyperliquid; with symbol: {symbol, venues: {bybit, okx, hyperliquid}}); a real captured example is free at https://x402.ochinimus.app/api/sample/get_funding_rate"New value: +"the get_funding_rate payload (without symbol: {sol, btc} from Hyperliquid; with symbol: {symbol, venues: {hyperliquid}}); a real captured example is free at https://x402.ochinimus.app/api/sample/get_funding_rate"

Changed2 schema fields changedSep 28, 2026

addedInput schema / properties / symbol

Added value: +{
+  "description": "USDT perp symbol e.g. ETHUSDT, ONDOUSDT (omit for SOL and BTC from Hyperliquid)",
+  "type": "string"
+}

changedOutput schema / properties / data / description

Previous value: -"the get_funding_rate payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_funding_rate"New value: +"the get_funding_rate payload (without symbol: {sol, btc} from Hyperliquid; with symbol: {symbol, venues: {bybit, okx, hyperliquid}}); a real captured example is free at https://x402.ochinimus.app/api/sample/get_funding_rate"

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "the get_funding_rate payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_funding_rate",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_funding_rate",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint, non-destructive), so the bar is lower. The description adds non-annotated behavior that matters operationally: a metered cost of 0.005 USDC per call and the x402 payment rails/ledgers accepted, which an agent must know before invoking.

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 dense, front-loaded sentences: what you get first, then the default behavior and price. The long enumeration of returned fields is partially redundant given an output schema exists, but it aids selection and nothing reads as filler.

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

Completeness4/5

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

An output schema exists, so return format needn't be explained, and cost/auth are covered. What remains unstated is freshness/real-time vs delayed pricing and any rate limits on the paid calls, minor gaps for an otherwise complete single-parameter read tool.

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?

With one parameter at 100% schema coverage, the baseline is 3. The description goes slightly beyond the schema by spelling out the no-symbol fallback behavior including that open interest is returned in that case, adding meaning the schema's terse 'omit for SOL and BTC' only implies.

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?

States a specific verb+resource ('Funding rate for any Hyperliquid perp') and enumerates the exact metrics returned, which makes it easy to distinguish from history/radar/extremes siblings by intent. It never explicitly names a sibling to contrast with, so it stops short of the top score.

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 description gives one conditional (omitting symbol falls back to SOL and BTC with open interest) and discloses the per-call cost, which is genuine usage context. However, it never says when to choose this over get_funding_history, get_funding_pulse, or get_funding_extremes, leaving alternative selection to inference.

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

All AgentFeed tools Inspect

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.