Skip to main content
Glama

get_live_l2_orderbook

Fetches real-time 60-level L2 order books, liquidity walls, and order-flow imbalance for crypto, stocks, ETFs, gold, or FX to reveal market microstructure and institutional pressure.

Instructions

Fetch real-time market microstructure & liquidity walls for Crypto, US/JP Stocks, ETFs, Gold, or FX. [日本語検索キーワード: リアルタイム60段板 / 板情報 / オーダーブック / 買い壁・売り壁 / 歩み値OFI / 出来高プロファイル POC VWAP]

  • For Crypto (e.g. 'BTC-USD', 'ETH-USD', 'SOL-USD', 'XRP-USD'): Returns live 60-level L2 limit order book (Coinbase -> Kraken -> Hyperliquid automatic fallback), Stoikov micro-price, spread (bps), Top-10 & Deep-60 Order Flow Imbalance (OFI), largest Bid/Ask liquidity walls in USD, and recent aggressive tape delta.

  • For Stocks / ETFs / Gold / FX (e.g. 'NVDA', 'TSLA', 'SPY', 'GLD', '7203.T', 'USDJPY'): Returns live 5-minute Volume-at-Price (VAP) Point of Control (POC), 70% Value Area (VAH/VAL), Session VWAP deviation (bps), institutional accumulation/distribution pressure, and local Moomoo OpenD (:11111) NASDAQ TotalView port readiness.

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_live_l2_orderbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNo
symbolNoBTC-USD

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations the description carries the full burden, and it does disclose genuinely useful behavior: an automatic exchange fallback chain (Coinbase -> Kraken -> Hyperliquid) and a local dependency on Moomoo OpenD :11111 for NASDAQ TotalView. It omits other behavioral facts an agent needs — rate limits, latency/staleness, whether the equities path degrades or fails when the local bridge is absent, and any auth requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, and the per-asset-class bullets are a reasonable structure. But the bracketed Japanese SEO keyword line is inventory padding that costs tokens without informing tool selection, and the dense jargon list (Stoikov micro-price, OFI, POC, VAH/VAL) is presented as output content the output schema already covers.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool this is largely sufficient, and an output schema exists so return values did not need spelling out. The gaps that remain are the ones that actually block correct invocation: what `depth` does, whether the equities branch requires a running local service, and how this differs from the sibling quant tools.

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 description coverage is 0%, so the description must compensate, and it only partly does: the repeated "60-level" phrasing implies the default depth and the example tickers cover symbol formats well. The `depth` parameter is never named, bounded, or explained, and its meaning on the equities/FX VAP path (where depth would presumably change the price-bucket granularity) is left entirely undefined.

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 opening line gives a concrete verb and resource ("Fetch real-time market microstructure & liquidity walls") plus the covered asset classes, and the two bullets spell out exactly what payload each asset class returns. It does not explicitly contrast itself with the sibling tools (candle packet, liquidity anomaly scan), so an agent must infer the boundary rather than be told it.

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 implied through asset-class enumeration — an agent can tell this tool applies to crypto and to stocks/ETFs/Gold/FX. However, there is no when-not guidance, no statement of prerequisites (e.g. that the equities path depends on a local Moomoo OpenD instance being up), and no routing versus the sibling tools, which is precisely where a multiplexed market-data server needs guidance.

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