Skip to main content
Glama

WhaleScope MCP

by io.github.osindo-dev

Deteksi Regime Pasar (Trending/Ranging/Breakout/Accumulation/Distribution)

binance_market_regime
Read-only

Klasifikasi 1 dari 6 regime (TRENDING_UP/DOWN, RANGING, BREAKOUT, ACCUMULATION, DISTRIBUTION) dari ADX(14), tren OI, CVD, dan spike volatilitas/volume (10 candle terakhir vs 10 sebelumnya PADA TIMEFRAME YANG SAMA, bukan baseline historis persisten). Panggil ulang dengan interval beda (mis. 1h lalu 4h) untuk regime independen per timeframe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesSimbol pair Binance Futures, contoh: BTCUSDT, ETHUSDT. Harus pair perpetual yang terdaftar di Binance USDS-M Futures.
intervalNoTimeframe candle untuk analisis regime (ADX, OI-change, CVD, volatility/volume spike): 1m, 5m, 15m, 30m, 1h, 2h, 4h, 6h, 12h, 1d. Default '1h'.1h

TDQS

A4.4/5.0
Behavior4/5

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

Annotations readOnlyHint=true dan openWorldHint=true sudah menandakan operasi aman; deskripsi menambah nilai dengan mengungkapkan metodologi penting, yaitu perhitungan spike volatilitas/volume dibandingkan 10 candle sebelumnya pada timeframe yang sama, bukan baseline historis persisten. Tidak ada kontradiksi dengan 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?

Deskripsi hanya dua kalimat, langsung menyampaikan tujuan, indikator, output, dan caveat penting. Tidak ada pengulangan informasi schema atau kata mubazir; setiap bagian berkontribusi.

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?

Deskripsi cukup lengkap untuk tool 2-parameter tanpa output schema: menyebutkan daftar output, input, metodologi, dan perilaku per-timeframe. Kekurangan kecil adalah tidak menjelaskan format/struktur nilai kembalian, tetapi daftar regime sudah cukup untuk penggunaan dasar.

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 100% dan kedua parameter sudah didokumentasikan lengkap dengan enum, default, dan contoh. Deskripsi menambah makna bahwa interval menentukan regime independen, sehingga agent tahu untuk memanggil ulang dengan interval berbeda. Ini melampaui informasi skema.

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?

Deskripsi menyatakan secara spesifik bahwa tool mengklasifikasikan 1 dari 6 regime pasar (TRENDING_UP/DOWN, RANGING, BREAKOUT, ACCUMULATION, DISTRIBUTION) menggunakan ADX, tren OI, CVD, dan spike volatilitas/volume. Ini membedakannya dari sibling-sibling yang fokus pada data mentah atau analisis spesifik lainnya, tanpa tautologi.

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?

Deskripsi memberikan panduan eksplisit untuk memanggil ulang dengan interval berbeda guna mendapatkan regime independen per timeframe. Konteks penggunaan cukup jelas, meskipun tidak menyebutkan kapan tidak menggunakan tool ini atau alternatif yang lebih cocok.

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