Skip to main content
Glama

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Funding history

get_funding_history
Read-onlyIdempotent

Funding rate history for any USDT perp, up to 200 intervals: the average rate, its annualized %, the share of intervals that were positive, and the raw series. What the carry has actually been. Costs 0.005 USDC per call (x402, USDC on Solana or Base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNointervals, 1-200, default 30
symbolNoUSDT perp symbol e.g. SOLUSDT, BTCUSDT (default SOLUSDT)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesthe get_funding_history payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_funding_history
toolYesthe tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / symbol / description
      Previous value: -"USDT perp symbol e.g. SOLUSDT"New value: +"USDT perp symbol e.g. SOLUSDT, BTCUSDT (default SOLUSDT)"
    • removedInput schema / required
      Removed value: -[
-  "symbol"
-]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "the get_funding_history payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_funding_history",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_funding_history",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover read-only, open-world and idempotent traits, so the description earns credit for adding what they cannot: a per-call price (0.005 USDC via x402 on Solana or Base). That payment/cost disclosure is genuinely useful behavioral context an agent needs before calling. It stops short of mentioning rate limits or history depth beyond 200.

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?

Three sentences, front-loaded with the purpose and result fields, then cost. 'What the carry has actually been' is slightly decorative but reinforces intent rather than wasting a slot.

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

Completeness3/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 values need not be explained, and pricing is covered. What is missing is sibling differentiation and any statement of history boundaries beyond the 200-interval cap, leaving the agent under-equipped to choose this over get_funding_rate.

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 description coverage is 100%, and the schema already documents limit (1-200, default 30) and symbol (default SOLUSDT). The description's 'up to 200 intervals' and 'any USDT perp' merely echo that, adding no syntax or format meaning. Baseline 3 applies when the schema carries the load.

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 and resource ('funding rate history for any USDT perp') and even enumerates the returned quantities, so the purpose is unambiguous. However, it never distinguishes itself from the several funding-named siblings (get_funding_rate, get_funding_pulse, get_funding_extremes, get_funding_cross), which is where an agent is most likely to misfire.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not, or alternative named. The 'history' framing implies a retrospective use case, but with four sibling funding tools the absence of routing guidance is a real gap.

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

All AgentFeed 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