Skip to main content
Glama

WhaleScope MCP

by io.github.osindo-dev

Order Book Depth (Spot)

binance_get_spot_order_book
Read-only

Snapshot order book (bid/ask) real-time SPOT. Versi Spot dari binance_get_order_book_depth -- bandingkan wall/likuiditas spot vs futures. Default ringkas (top 10 + spread); detail: "full" untuk semua level sampai limit. PENTING: snapshot SESAAT, order book berubah cepat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoJumlah level bid/ask yang diambil per sisi. Harus salah satu dari: 5, 10, 20, 50, 100, 500, 1000, 5000.
detailNo'summary' (default): metrik turunan + <=10 poin terbaru saja, HEMAT TOKEN. 'full': array/level mentah lengkap seperti sebelumnya. Lihat docs/tool_response_reference.md.summary
symbolYesSimbol pair Binance Futures, contoh: BTCUSDT, ETHUSDT. Harus pair perpetual yang terdaftar di Binance USDS-M Futures.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds that the snapshot is transient ('PENTING: snapshot SESAAT, order book berubah cepat') and explains the summary vs full behavior. This adds valuable behavioral context beyond annotations without contradiction.

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 informative yet compact, with a clear intro, a differentiation note, and a prominent warning. It's not overly verbose and each sentence contributes value. The only minor issue is a slight redundancy with the schema for 'detail', but it's acceptable.

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?

There is no output schema, but the description explains what summary vs full returns (top 10 + spread vs raw arrays) and references docs. For a real-time order book tool, this is adequate context; it could add more detail on exact data structure but is sufficient for agent use.

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 coverage is 100% with descriptions for all params. The description adds meaning by explaining the effect of 'detail' (summary saves tokens, full gives all levels up to limit) and ties limit to the full option. It clarifies the intended use of each parameter beyond the schema definitions.

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?

Description clearly states it's a real-time SPOT order book snapshot, and explicitly distinguishes from the futures version (binance_get_order_book_depth) for comparing spot vs futures walls/liquidity. The verb 'Snapshot' and resource 'order book' are specific, and it differentiates from siblings.

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?

Provides guidance on when to use (spot vs futures comparison) and how to use (summary vs full detail). It doesn't explicitly name alternatives beyond the futures version, but the context is clear enough for an agent to decide between spot and futures order books. It could be more explicit about when to avoid this tool, but overall conveys usage context.

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