Skip to main content
Glama
romudille-bit

AgentPay x402 — Economic-intelligence layer for AI Agents

by romudille-bit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

orderbook_depth

Read-onlyIdempotent

Estimate slippage for large trades by checking real bid/ask depth at $10k, $50k, and $250k notionals on Binance and Bybit before sizing a position.

Instructions

Get real bid/ask depth and slippage estimates at $10k, $50k, and $250k notional from Binance and Bybit. Use before sizing a position to know if you can execute without moving the market.

Use when: You need to estimate slippage before executing a large trade. Tells you how much a $10k, $50k, or $250k order will move the market. Not for: you need market cap or 24h volume — token_market_data; a full pre-trade verdict at your size — pre_trade_check. Centralised-exchange books (Binance/Bybit) only, not DEX pools. Returns: best_bid, best_ask, spread_pct, depth with slippage_pct at $10k/$50k/$250k notional, per-exchange best prices Example response: {"asset": "ETH", "pair": "ETH/USDT", "best_ask": 2071.5, "best_bid": 2071.2, "spread_pct": 0.0145, "depth": [{"notional_usd": 10000, "slippage_pct": 0.002, "executable": true}, {"notional_usd": 50000, "slippage_pct": 0.008, "executable": true}, {"notional_usd": 250000, "slippage_pct": 0.031, "executable": true}], "exchanges": [{"exchange": "Binance", "best_ask": 2071.5, "best_bid": 2071.2}, {"exchange": "Bybit", "best_ask": 2071.6, "best_bid": 2071.1}], "source": "binance/bybit"}

Price: free. Read-only live public data; no API key, nothing signed or spent. Fails with an error message on an unknown symbol or an unreachable upstream source.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetYesToken symbol, e.g. 'BTC', 'ETH', 'SOL'ETH

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.2
    • addedInput schema / properties / asset
      Added value: +{
+  "default": "ETH",
+  "description": "Token symbol, e.g. 'BTC', 'ETH', 'SOL'",
+  "type": "string"
+}
    • removedInput schema / properties / exchange
      Removed value: -{
-  "default": "binance",
-  "description": "Exchange to query: binance (default) or bybit",
-  "type": "string"
-}
    • removedInput schema / properties / symbol
      Removed value: -{
-  "description": "Trading pair, e.g. ETHUSDT or BTCUSDT",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "symbol"
-]New value: +[
+  "asset"
+]
  2. Addedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld, but the description adds substantive context beyond them: free pricing, no API key, nothing signed or spent, CEX-only constraint (not DEX), and explicit error behavior on unknown symbols or unreachable upstreams. This is well above the bar.

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?

Front-loaded purpose followed by clearly labelled 'Use when', 'Not for', 'Returns', and example blocks. Every section earns its place; length is justified by the coverage it provides.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 fully specifies return fields, a concrete example response, cost/auth profile, and failure modes. An agent has everything needed to invoke and interpret this tool correctly.

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 100% and only one parameter exists, so the schema already documents 'asset'. The description only reinforces this via the example ('ETH'), adding no syntax or format detail beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb (Get) with precise resource and scope: real bid/ask depth and slippage at $10k/$50k/$250k notional from Binance and Bybit. Explicitly differentiates from siblings token_market_data (market cap/24h volume) and pre_trade_check (full pre-trade verdict).

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

Usage Guidelines5/5

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

Provides explicit when-to-use ('before sizing a position', 'before executing a large trade') and when-not-to-use clauses that name the correct alternative tools for each excluded case. No inference required.

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

Deploy Server

Other Tools