Gemral Edge

Crypto Funding Rate Extremes

get_crypto_funding_extremes

Top cryptocurrency perpetual futures contracts with extreme positive or negative funding rates across exchanges. Sourced from live exchange funding intervals. Read-only evidence.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_crypto_funding_extremes"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`direction`	No	Direction of funding extremes	negative

Output Schema

Name	Required	Description
`notice`	No	Free-tier upgrade notice; only when results are masked/delayed.
`results`	Yes	Tool result payload (read-only evidence). Shape varies by tool; scoring weights are never exposed.
`history_limit`	No	Present when the license limits history depth: earliest_allowed date, history_days and how many older items were removed.
`deprecated_fields`	No	Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / deprecated_fields

Added value: +{
+  "description": "Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

First observedOct 23, 2026

TDQS

C2.5/5.0

Behavior1/5

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

The description asserts 'Read-only evidence,' but the annotations declare readOnlyHint=false, which directly contradicts that claim. Beyond that, 'sourced from live exchange funding intervals' is the only behavioral context, and it does not clarify freshness, snapshot vs. streaming behavior, or pagination.

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 short sentences, front-loaded with the core subject. The only wasted sentence is 'Read-only evidence,' which is both redundant with (and contrary to) the annotations.

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

Completeness2/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 described, but key calling information is missing: what threshold makes a rate 'extreme', whether results are cross-exchange ranked or per-exchange, and what `limit` caps. For a data-discovery tool with a partially documented schema, this leaves real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: `direction` has an enum description while `limit` is undocumented in both schema and description. The description does not explain the default direction ('negative'), the meaning of 'top' for the limit, or how many extremes are returned relative to limit.

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?

The description names a specific resource (perpetual futures funding-rate extremes across exchanges) and its scope (top contracts, positive or negative). It is clear what the tool surfaces, but it makes no attempt to distinguish itself from the closest sibling, scan_crypto_patterns, or to state how 'extreme' is defined.

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 statement of when to use this tool versus alternatives, no prerequisites, and no mention of the sibling tools that overlap with crypto signal discovery. The agent must infer usage entirely from the resource name.

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

All Gemral Edge 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.