Skip to main content
Glama
Sign In

Swiftedge order flow

by uk.swiftedge
OverviewDiscussionsAdmin

Funding and open interest

get_funding_and_open_interest
Read-only

Funding rate (8-hour and annualized), next funding time, funding history, open interest with 1/4/24-hour change and its history.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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 the returned data scope (funding history, OI history, 1/4/24-hour changes), but it does not disclose history depth, time granularity, pagination, or rate limits.

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 compact sentence lists the returned metrics with no filler. It is front-loaded and appropriately sized for a one-parameter read tool.

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 one-parameter read-only tool with no output schema, the description covers the main return values an agent needs to select it. It omits history length and time granularity, which would be helpful but are not essential for selection.

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 the single market parameter is fully documented with an enum. The description adds no parameter-specific meaning beyond the schema.

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?

The description names the specific metrics returned—funding rate (8-hour and annualized), next funding time, funding history, open interest with 1/4/24-hour change and its history—so the resource is clear. It does not explicitly distinguish this from siblings like get_market_snapshot or get_markets_overview, so it stops short of a 5.

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

Usage Guidelines2/5

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

No sentence states when to choose this tool over get_market_snapshot, get_markets_overview, or other siblings, nor any prerequisites. Usage is only implied by the metric names.

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