QuantXData MCP Server

get_ob_l2_snapshot

Retrieve a Level 2 order book snapshot for a cryptocurrency pair on a specified exchange, with configurable depth to control the number of price levels.

Instructions

Get L2 order book snapshot with configurable depth

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fsym": "<fsym>",
      "tsym": "<tsym>",
      "e": "<e>"
    },
    "name": "get_ob_l2_snapshot"
  }
}

Input Schema

Name	Required	Description
`e`	Yes	Exchange name
`fsym`	Yes	From symbol
`toTs`	No	End timestamp (Unix)
`tsym`	Yes	To symbol
`limit`	No	Depth (number of price levels, default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'snapshot' (which is also in the name) but adds nothing about read-only implications, return shape, rate limits, or other behavioral nuances.

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?

The description is a single, front-loaded sentence with no wasted words. It directly conveys the core purpose and the one differentiating feature.

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?

The tool has 5 parameters and no output schema or annotations, but the description is minimally viable for a simple snapshot tool. However, it omits details about the return format and does not differentiate from sibling tools, leaving some contextual gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides 100% parameter descriptions, so the baseline is 3. The description's 'configurable depth' maps to the 'limit' parameter but does not add meaningful extra semantics beyond what the schema already states.

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 clearly states 'Get L2 order book snapshot' with a specific verb and resource, and 'L2' distinguishes it from L1 and generic order book tools. The configurable depth aspect further clarifies its scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like get_ob_l1_top or get_orderbooks. The usage is only implied by the name and the brief 'configurable depth' note, with no explicit exclusions or alternative recommendations.

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

Deploy Server