Skip to main content
Glama

APEX Runner Crypto Signals

funding_rate

$0.007 — Aggregate perpetual funding rate signal across crypto exchanges. Returns 8h rate, annualized %, and long/short pressure.

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": "funding_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden, and it does disclose the returned fields and the aggregation scope. It says nothing about freshness/latency, which exchanges are covered, weighting methodology, or whether the signal is cached, which matters for a market-data signal tool.

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 compact sentences that front-load the domain and enumerate the returns, with no filler or repetition. The one piece of waste is the leading '$0.007' price token, which is irrelevant to an agent deciding whether to call the tool.

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?

For a zero-parameter read-only signal with no output schema, the description supplies what the agent needs: what is aggregated, over which venue class, and what comes back. Missing only secondary context like update cadence and exchange coverage, which is minor at this complexity.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly spends no space on inputs.

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 resource and scope: an aggregate perpetual funding rate signal across crypto exchanges, plus the concrete outputs (8h rate, annualized %, long/short pressure). The word 'aggregate ... across crypto exchanges' implicitly separates it from the exchange-specific sibling funding_rate_hl, though it never names that alternative.

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?

Usage is only implied: 'aggregate ... across crypto exchanges' suggests picking this when a cross-exchange consensus view is wanted rather than a single-venue rate. There is no explicit when-to-use, when-not, or named alternative, so the agent must infer the routing decision.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources