Skip to main content
Glama
Sign In

Swiftedge order flow

by uk.swiftedge
OverviewDiscussionsAdmin

Live order book depth

get_order_book
Read-only

The live order book grouped by price level: the largest bids and asks within range_pct of price, total resting USD on each side and the bid/ask imbalance.

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": {
      "market": "<market>"
    },
    "name": "get_order_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelsNoLargest price levels to return per side (1-25)
marketYesMarket: btc, gold, eth, sol, xrp, us500, us100, silver, oil
range_pctNoHow far from price to look, in percent (0.1-3)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real behavioral context by defining the aggregation (grouped by price level), the bounded window (within range_pct of price), and the derived metrics (resting USD per side, imbalance). It does not say whether 'live' means a point-in-time snapshot or a streaming/refreshable view, which is the main remaining gap.

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?

A single front-loaded sentence with no filler, and the key framing ('grouped by price level') comes first. It is dense rather than wasteful, though the trailing list of returned fields would read better as separate clauses.

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 must convey returns, and it does name the payload fields; annotations cover the read-only nature and the schema covers all parameters. What is missing is snapshot-vs-live semantics and ordering of the returned levels, which matter for a depth tool.

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 market, levels and range_pct are already fully documented with defaults and bounds. The description only lightly reinforces range_pct as a distance-from-price window; it adds no new parameter meaning such as ordering or tie-breaking behavior, so the baseline 3 applies.

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?

States a specific resource ('live order book grouped by price level') and enumerates what it returns: largest bids/asks within range_pct, total resting USD per side, bid/ask imbalance. That is specific enough to separate it from get_candles, get_large_trades and get_key_levels, but 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 only implied: an agent must infer that this is the tool for near-price liquidity/depth, while get_market_snapshot or get_key_levels cover other views. There is no explicit when-to-use, when-not-to-use, or named alternative.

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

All Swiftedge order flow toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources