Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

analyze_crypto_orderbook_arbitrage

Read-onlyIdempotent

Analyze live Level-2 crypto order books across major exchanges to measure $10k/$50k/$100k slippage and detect cross-exchange arbitrage spreads.

Instructions

Analyze live Level-2 cryptocurrency order book depth, $10k/$50k/$100k execution slippage basis points, and cross-exchange arbitrage spreads across Binance, Bybit, Kraken, Coinbase, OKX, and KuCoin.

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": {
      "symbols": "<symbols>"
    },
    "name": "analyze_crypto_orderbook_arbitrage"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesTrading pair symbols in uppercase (e.g., ["BTCUSDT", "ETHUSDT", "SOLUSDT"]).
exchangesNoSpot exchanges to compare for order book depth and arbitrage.
maxResultsNoMaximum number of order book and spread records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

A3.8/5.0
Behavior3/5

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

The supplied annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and repeatability profile is fully covered and the description does not need to restate it. What it adds beyond that is the "live" data characteristic and the fact that it computes derived metrics (slippage in bps at fixed notional tiers, spread), which is useful. It says nothing about data freshness/staleness, latency, venue outage handling, or whether missing symbols are dropped or errored, which for a multi-exchange live-quote tool would be the genuinely valuable additions.

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?

A single dense sentence with no filler, and it front-loads the primary resource (order book depth) before the derived metrics and the venue coverage. Every clause contributes a distinct piece of information an agent needs for selection.

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 three-parameter, read-only analysis tool with rich annotations, the definition covers input scope and the metrics produced well enough to invoke it correctly. The main residual gap is that no output schema exists, so the description could say more about the shape of returned records (per-symbol? per-venue? both) rather than only listing the computed quantities.

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 100%, so all three parameters (symbols, exchanges, maxResults) are already documented in the schema, making a baseline of 3 appropriate. The description adds marginal meaning by naming the full exchange universe and revealing the hard-coded notional tiers ($10k/$50k/$100k) that shape the slippage output, but it does not clarify symbol format, the 20-symbol cap, or what maxResults truncates.

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 uses a specific verb ("Analyze") over three named resources: Level-2 order book depth, execution slippage in basis points at $10k/$50k/$100k notional tiers, and cross-exchange arbitrage spreads. It also enumerates the six venues covered (Binance, Bybit, Kraken, Coinbase, OKX, KuCoin), so an agent can immediately tell this apart from every sibling tool, none of which touch crypto order books.

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 only implied: the word "live" and the metric list suggest this is for real-time microstructure/arbitrage analysis rather than historical or DeFi-yield questions. There is no explicit when-to-use clause, no when-not-to-use exclusion, and no routing to or from related siblings such as monitor_defi_yield_and_tvl or scan_dex_token_security, leaving the boundary to inference.

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