Skip to main content
Glama

Microverse Market Data

Compare one asset across venues

compare_venues
Read-onlyIdempotent

Top of book for one asset (e.g. 'BTC', 'SOL') on every crypto exchange we carry, in one quote currency (USDT by default; 'USD' for Coinbase, Gemini and Bitfinex). Returns each venue's best bid/ask, spread in bps, deviation from the median mid, plus the consolidated best bid and offer (which venues hold them) and whether the venues are crossed (an apparent arbitrage).

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": "compare_venues"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYes
quoteNoUSDT

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, so the bar is lower. The description goes beyond them by enumerating what data is returned (best bid/ask, spread in bps, deviation from median mid, which venues hold the consolidated BBO, crossed/arbitrage flag), which tells an agent it is a snapshot, not a depth or streaming feed. It omits staleness, rate limits, and how venues without a market for the asset are handled.

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?

One dense but front-loaded sentence that leads with the scope and then enumerates outputs; no filler. It is long enough that a slight structural break between inputs and returned fields would help scanning, but nothing is redundant.

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 2-parameter read-only tool with no output schema, the description carries the return-value burden well by listing the per-venue and consolidated fields. The remaining gap is edge-case behavior (missing venues, unsupported assets, snapshot timing), which is minor for this complexity.

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 description coverage is 0%, and the description partly compensates: it gives example asset values ('BTC', 'SOL') and explains the quote parameter's default and the venue-specific USD case. It does not state the expected format, case sensitivity, or what happens when an asset or quote pair is unsupported, so meaning is added but not fully.

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?

Specific verb+resource+scope: 'Top of book for one asset ... on every crypto exchange we carry,' with the quote-currency dimension spelled out. An agent can distinguish this from a single-venue book or a consolidated book because the description names the per-venue-then-consolidated structure it returns.

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 context is implied by the market-data framing and the note that USDT is the default while USD applies to Coinbase, Gemini and Bitfinex, which is genuinely helpful routing for the quote parameter. There is no explicit when-to-use/when-not guidance and no named alternative for single-venue or consolidated queries, so selection between overlapping siblings is left to inference.

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