Skip to main content
Glama

BitTalk News

get_order_walls

Read-onlyIdempotent

Large limit orders (walls) in the Binance + Bybit order book, spot and futures: bid/ask side, price range, USD size, whether active now. Crypto only. An order-book fact, not a forecast. lang — ru or en; default en.

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": {
      "asset": "<asset>"
    },
    "name": "get_order_walls"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
assetYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "default": "en",
      +  "title": "Lang",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already state readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful framing beyond that: the data sources, the spot/futures scope, the bid/ask orientation, and which attributes are reported (price range, USD size, active status).

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 dense and front-loaded: it names the resource, sources, markets, what is reported, the scope limit, and the epistemic framing in a few compact clauses with no filler.

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?

For a 3-parameter, read-only, closed-world tool with no output schema, the description conveys enough to invoke it correctly and to anticipate the returned fields. The only shortfall is the unexplained limit parameter and the absence of detail on how the two exchanges are combined in the response.

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?

Schema coverage is 0%, so the description bears the burden of explaining parameters; it does clarify that lang accepts ru or en and defaults to en, which is useful. It says nothing about asset or limit (default 20), so the meaning of limit as the maximum number of walls returned must be inferred.

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 concrete verb and resource: it retrieves large limit orders (walls) from the Binance and Bybit order books, spot and futures, and it frames the result as a factual order-book observation rather than a forecast, which clearly separates it from get_forecast.

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?

It gives the key qualifying context: crypto only and a present-tense fact rather than a prediction, which tells the agent when this tool is appropriate. It does not, however, explicitly name a sibling to use instead when the request is about forecasts or support/resistance levels.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources