whale-insights

funding_rate_monthly

Read-onlyIdempotent

Funding rate permanent monthly archive — Returns the permanent monthly archive of perpetual funding rates per token — one row per token per calendar month, aggregated from daily snapshots before purge. Never deleted; covers the top 10 tokens by volume. Optional ?symbol=BTC to filter. Each row includes: month, symbol, avgRate, minRate, maxRate, dominantSentiment (bullish/neutral/bearish based on avg rate), daysInMonth. Months with fewer than 20 daily records are excluded. No authentication required. 60 req/min. 5-min cache. — Use this for long-term monthly archive data; use the corresponding live or daily-history tool for current or finer-grained data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	No	Token symbol to filter by (e.g. BTC, ETH). Omit to return all top-10 tokens.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	No
`months`	No
`symbol`	No
`updatedAt`	No
`dataSource`	No
`attribution`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "attribution": {
+      "$ref": "#/components/schemas/Attribution"
+    },
+    "dataSource": {
+      "type": "string"
+    },
+    "months": {
+      "items": {
+        "properties": {
+          "avgRate": {
+            "type": "number"
+          },
+          "daysInMonth": {
+            "type": "integer"
+          },
+          "dominantSentiment": {
+            "type": "string"
+          },
+          "maxRate": {
+            "type": "number"
+          },
+          "minRate": {
+            "type": "number"
+          },
+          "month": {
+            "format": "date",
+            "type": "string"
+          },
+          "symbol": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "symbol": {
+      "nullable": true,
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJun 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds substantial context beyond that: data is aggregated before purge, never deleted, limited to top 10 tokens by volume, months with fewer than 20 records are excluded, no authentication required, 60 req/min rate limit, and 5-min cache. These are exactly the behavioral traits an agent needs to invoke it safely and interpret results.

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?

The description is dense and front-loaded with the core purpose, followed by row structure, coverage constraints, operational limits, and usage guidance. It is somewhat redundant with the phrase "permanent monthly archive" appearing twice early on, but every sentence otherwise carries useful information.

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?

For a one-optional-parameter read-only tool with an output schema, this description is complete. It covers what data is returned, aggregation logic, exclusions, coverage scope, authentication, rate limits, caching, and the appropriate alternative tool. Nothing essential is missing for an agent to call it correctly.

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%, so the schema already documents the optional symbol parameter. The description adds only a concrete example (?symbol=BTC) and confirms omission returns all top-10 tokens, which is useful but not a major semantic expansion beyond the schema.

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 specifies a clear verb and resource: "Returns the permanent monthly archive of perpetual funding rates per token" with one row per token per month. It also distinguishes itself from siblings by explicitly positioning this as the long-term monthly archive versus the corresponding live or daily-history tool.

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?

The description explicitly directs usage: "Use this for long-term monthly archive data; use the corresponding live or daily-history tool for current or finer-grained data." This tells an agent exactly when to select this tool over alternatives.

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

All whale-insights 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?