Skip to main content
Glama

Microverse Market Data

Get consolidated order book

get_consolidated_book
Read-onlyIdempotent

Depth merged across every live crypto exchange for one asset: at each price, the total size and the size per venue. exclude_venues is a comma-separated list of venue ids to leave out. Venues whose price is far from the others (usually a stale book) are left out unless include_outliers is true.

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

Input Schema

NameRequiredDescriptionDefault
assetYes
depthNo
quoteNoUSDT
exclude_venuesNo
include_outliersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), so the bar is lower; the description still adds meaningful behavior the annotations do not: outlier/stale venues are silently dropped from results unless include_outliers is true. That is exactly the kind of result-shaping behavior an agent would otherwise misread as missing liquidity.

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?

Three tight sentences, front-loaded with the output shape before parameter notes. No filler; only mild compression cost in the phrase 'Depth merged across every live crypto exchange'.

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?

With no output schema, the description does the right thing by sketching the return shape (total size and per-venue size at each price). But key call parameters (depth, quote) are undocumented and there is no note on ordering or how venues are identified, leaving gaps for a 5-parameter aggregation tool.

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 carries the full burden, yet it only clarifies exclude_venues (comma-separated venue ids) and include_outliers. asset, quote, and especially depth (integer, default 20) are left undefined — whether depth means price levels per venue or a merged level count is ambiguous and materially changes interpretation.

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?

Names a specific resource and output: depth merged across every live crypto exchange for one asset, with total size and per-venue size at each price. The 'consolidated' framing implicitly distinguishes it from get_order_book (single venue), though no sibling is named explicitly.

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 by the 'merged across every live exchange' framing, which suggests it is the choice when cross-venue aggregate depth is wanted, but there is no explicit when-to-use versus get_order_book or compare_venues, and no stated prerequisites.

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