Skip to main content
Glama
Sign In

Swiftedge order flow

by uk.swiftedge
OverviewDiscussionsAdmin

Real liquidations

get_liquidations
Read-only

Liquidations that really happened in the last 1-24 hours: longs and shorts liquidated in USD, per hour and the 10 largest.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 the safety profile is covered. The description adds real value by disclosing the returned structure — long vs short liquidations in USD, hourly buckets, plus the 10 largest events — which the annotations cannot convey and no output schema exists to document.

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 the scope constraint front-loaded and no filler. Every clause (time window, long/short USD breakdown, hourly granularity, top 10) carries distinct information.

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 must describe returns, and it does so adequately for a two-parameter read tool: aggregation granularity and the top-10 list are both stated. Minor gaps remain around units/formatting of the hourly series and whether the 10 largest are ranked by size, but nothing critical to calling it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: the market enum is described in the schema, but the hours parameter is not. The description compensates by stating the 'last 1-24 hours' window, which conveys both the valid range and the default behavior of the undocumented parameter.

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 (liquidations) with scope (last 1-24 hours) and output shape (longs/shorts in USD, per hour, top 10). The phrase 'really happened' implicitly separates it from get_liquidation_heatmap, which shows modeled levels, but it never names that sibling 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 can infer this is for realized liquidation flow rather than predicted liquidation zones, but there is no explicit when-to-use statement, no mention of the heatmap alternative, and no note on when a shorter vs longer window is appropriate.

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