Crypto Bot Audit + Market Data (x402 paid)

OKX perpetual funding

market_okx_funding_rate

Read-onlyIdempotent

Current and next funding rate for an OKX perpetual, with the settlement timestamps and the funding band the venue caps it at. Costs $0.001 USDC per call. Byte-identical to GET /market/okx-funding-rate?instId=BTC-USDT-SWAP.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`instId`	Yes	OKX perpetual swap id [required]

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`note`	No
`found`	No
`stale`	No
`caveat`	No
`instId`	No
`method`	No
`reason`	No
`source`	No
`premium`	No
`instType`	No
`settState`	No
`formulaType`	No
`fundingRate`	No
`fundingTime`	No
`impactValue`	No
`interestRate`	No
`maxFundingRate`	No
`minFundingRate`	No
`nextFundingTime`	No
`prevFundingTime`	No
`settFundingRate`	No
`fundingRate8hPct`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "formulaType": {
+      "type": "string"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "fundingRate": {
+      "type": "string"
+    },
+    "fundingRate8hPct": {
+      "type": "number"
+    },
+    "fundingTime": {
+      "type": "integer"
+    },
+    "impactValue": {
+      "type": "string"
+    },
+    "instId": {
+      "type": "string"
+    },
+    "instType": {
+      "type": "string"
+    },
+    "interestRate": {
+      "type": "string"
+    },
+    "maxFundingRate": {
+      "type": "string"
+    },
+    "method": {
+      "type": "string"
+    },
+    "minFundingRate": {
+      "type": "string"
+    },
+    "nextFundingTime": {
+      "type": "integer"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "premium": {
+      "type": "string"
+    },
+    "prevFundingTime": {
+      "type": "integer"
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "settFundingRate": {
+      "type": "string"
+    },
+    "settState": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "ts": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses a $0.001 USDC cost per call and states the response is byte-identical to a specific GET endpoint, which is actionable behavioral information. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences front-load the core data fields, then add cost and endpoint equivalence. Every sentence earns its place with no redundancy.

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 one required parameter, rich annotations, and an output schema present, the description covers cost, exact API equivalence, and returned fields. Nothing essential is missing for an agent to select and invoke it correctly.

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?

Schema coverage is 100% and the single instId parameter is documented. The description adds value by embedding an example instId (BTC-USDT-SWAP) in the equivalent endpoint, illustrating the expected format.

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?

The description states a specific resource (OKX perpetual funding rate) and the exact data returned: current and next rates, settlement timestamps, and funding band. It is clearly distinguishable from sibling OKX market tools like market_okx_ticker or market_okx_candles.

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

Usage Guidelines4/5

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

The intended use is clear from the resource and data fields, and the byte-identical GET endpoint gives an agent an exact reference. It does not name alternatives or exclusion conditions, but the context is unambiguous enough to route selection.

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

All Crypto Bot Audit + Market Data (x402 paid) 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.

Resources

Need Help?