Skip to main content
Glama
Sign In

Realtap

by io.github.CSteenkamp
OverviewDiscussionsAdmin

Open perpetual positions

get_perps_positions
Read-onlyIdempotent

Open perp positions of traders (the venue's own liquidity vaults are left out), ordered by size, PnL, leverage, recency or liquidation risk. Amounts in USD.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_perps_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideNoOnly longs or only shorts.
sortNoOrdering of the positions.notional
limitNoHow many positions to return (1-50, default 15).
minUsdNoLeave out positions with a smaller notional value (USD).
symbolNoOnly this market, for example ADA-USD or ADA.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already disclose that this is a read-only, idempotent, non-destructive open-world operation. The description adds useful behavioral context by excluding the venue's own liquidity vaults and specifying USD amounts, but it does not describe return shape, pagination, or rate-limit behavior. With annotations covering the safety profile, this is adequate but not rich.

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?

The description is two short sentences with no filler. The key scoping detail, that venue liquidity vaults are excluded, is front-loaded alongside the resource being returned.

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 read-only list tool with full schema coverage and annotations, the description gives enough context to select and invoke it correctly. The main remaining gap is return format, but no output schema exists and the description's note about USD amounts and ordering partially compensates.

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 all five parameters and both enums are documented in the schema itself. The description restates the available ordering categories and USD denomination, but adds little syntax or meaning beyond what the schema already provides. The baseline of 3 is appropriate.

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 states a specific resource and scope: open perpetual positions of traders, excluding the venue's own liquidity vaults. It also explains ordering and that amounts are in USD, which clearly distinguishes it from a generic overview tool. However, it does not explicitly contrast itself with close siblings such as get_perps_overview or get_defi_positions.

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 implied by the phrase 'Open perp positions of traders' and the exclusion of venue vaults, so an agent can infer when this list tool is appropriate. It does not explicitly say when to use this versus alternatives like get_perps_overview or get_wallet_pnl, nor does it state any prerequisites or exclusions beyond the vault-omission note.

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

All Realtap 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