Skip to main content
Glama

WhaleScope MCP

by io.github.osindo-dev

Kecepatan Perubahan Funding Rate (OLS)

compute_funding_velocity
Read-only

Hitung kecepatan perubahan funding rate (per jam) via regresi linear (OLS) penuh atas window terakhir, PLUS lonjakan terbesar antar titik berurutan (maxStepDelta) -- nangkep spike-lalu-reversal yang bikin slope net mendekati nol tapi bukan berarti stabil. History diinjeksi caller (BUKAN fetch sendiri -- pass hasil binance_get_funding_rate_history). TIDAK ada label kategorikal, angka mentah saja.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoSimbol pair Binance Futures, contoh: BTCUSDT, ETHUSDT. Harus pair perpetual yang terdaftar di Binance USDS-M Futures.
fundingHistoryYes
velocityWindowIntervalsNoJumlah titik funding TERAKHIR yang dipakai buat regresi, default 4.

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint=true and openWorldHint=false, the description discloses the full OLS method, the additional maxStepDelta statistic, dependency on injected history, and the absence of categorical labels. This adds substantial behavioral context and does not contradict 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 dense sentences front-load the core purpose and follow with essential caveats about input injection and output format. No wasted words.

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?

The description covers the computation method, input requirement, and raw-number output. However, with no output schema, the exact returned fields (e.g., slope, maxStepDelta) are not explicitly enumerated, leaving slight ambiguity for an agent.

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 description coverage is 67%; the description compensates for the undocumented fundingHistory parameter by specifying it must come from binance_get_funding_rate_history. Symbol and velocityWindowIntervals semantics are already covered by the schema, so the added value is moderate.

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 computation: OLS regression over the last funding window to produce per-hour velocity, plus maxStepDelta for spike detection. It clearly differentiates from sibling fetch/classification tools by stating history is caller-injected and output is raw numbers, not categorical labels.

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?

Explicitly instructs the agent to pass the result of binance_get_funding_rate_history rather than fetching internally, defining a clear prerequisite and complementary sibling. It also explains why the metric matters (capturing spike-then-reversal when net slope is near zero), though it does not enumerate exclusions versus other analysis tools.

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

All WhaleScope MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Most tools map to a distinct Binance metric or analytic concept, and descriptions explicitly contrast near-neighbors (spot vs futures, snapshot vs delta, 'BEDA dari...' notes). A few pairs could still be confused—`binance_get_basis` vs `binance_get_basis_history` and `binance_get_agg_trades` vs `binance_get_recent_trades`—but their purpose differences are explained well enough for careful agents.

Naming Consistency4/5

The dominant pattern is `binance_<verb>_<object>` in snake_case, with consistent complementary pairs like `get_*` and `get_*_history`. There are minor style breaks: `orderbook` vs `order_book`, the `whalescope_*` prefix, and `whalescope_full_pipeline` which lacks a verb, but the overall structure is readable and predictable.

Tool Count1/5

56 tools cross the explicit '50+ tools' extreme threshold. Although the Binance Futures domain is broad, many tools are single-endpoint or single-metric wrappers—multiple klines variants, order book variants, and ticker variants—that could be consolidated into parameterized composite tools. The surface is far too large for most agents to navigate efficiently.

Completeness4/5

The public market-data and analytics surface is remarkably complete: klines, funding, open interest, long/short ratios, top-trader data, liquidations, basis, order book behavior, regime detection, and full pipeline scoring are all covered. The main gaps are documented limitations such as unavailable liquidation-by-price data and non-public account/execution tooling, but agents can work around them without dead ends.

Resources