Skip to main content
Glama
Sign In

Swiftedge order flow

by uk.swiftedge
OverviewDiscussionsAdmin

Large market orders, last 24 hours

get_large_trades
Read-only

Large aggressive market orders in the last 24 hours: buy and sell totals, per hour, the 10 largest and the 10 latest.

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

Input Schema

NameRequiredDescriptionDefault
marketYesMarket: btc, gold, eth, sol, xrp, us500, us100, silver, oil

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so the description adds real context: the window is fixed at 24 hours (not parameterized), only aggressive/taker orders qualify, and the response shape is summarized. It doesn't state update cadence or whether the window is rolling.

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?

One sentence, colon-delimited, with the scope front-loaded and the payload contents enumerated. No filler.

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?

With no output schema, the description smartly describes what comes back (totals, hourly breakdown, top 10 largest, 10 latest), which is enough to call and interpret it. Minor gaps: fixed 24h window and freshness are not stated.

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% with an enum listing all nine markets, so the schema fully documents the single parameter. The description adds nothing about the market argument (e.g. case handling or defaults), 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 (large aggressive market orders) with a fixed time scope (last 24 hours) and enumerates the payload (buy/sell totals, per-hour, 10 largest, 10 latest). This clearly separates it from siblings like get_order_book or get_liquidations, 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 only implied: 'large aggressive market orders' signals flow/large-print analysis, but the description never says when to prefer this over get_order_book, get_liquidations, or get_market_snapshot, nor any prerequisites or exclusions.

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