Realtap

Trades on all DEXes, large trades

list_market_trades

Read-onlyIdempotent

Settled swaps on every Cardano DEX, newest first, optionally only those of at least minAda ADA ("large trades", "whale trades") or on one DEX. window is how far back to look (default 24 hours). Each trade has the time, DEX, the token traded (see tokenUnits for units), amounts, price and value in ADA and USD, the trader's stake address, the app that built the order and the transaction hash. For the trades of one token, pool or wallet use get_recent_trades.

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": "list_market_trades"
  }
}

Input Schema

Name	Required	Description	Default
`dex`	No	Only this DEX, by its name as `list_dexes` returns it.
`limit`	No	How many trades to return (1-50, default 10).
`cursor`	No	Value of `nextCursor` from the previous call, to get the next page.
`minAda`	No	Only trades worth at least this many ADA (for example 10000).
`window`	No	How far back to look.	24h

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds ordering ('newest first'), the default lookback (24h) and a full enumeration of returned fields, which matters because there is no output schema. It omits any note about result caps, latency, or how paging terminates.

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?

Two tightly packed sentences that front-load the scope and default, then the sibling routing. The return-field enumeration is long but earns its place given the absent output schema; nothing is 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 compensates by listing the fields of each trade and by pointing at `tokenUnits` for units. Combined with the schema's cursor/limit docs, an agent has enough to call and page correctly; only paging behavior and result-cap semantics are left implicit.

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%, so every parameter is already documented in the input schema. The description restates window's meaning and maps minAda to the colloquial 'large trades'/'whale trades', but adds no format or edge-case detail beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource and scope: 'Settled swaps on every Cardano DEX, newest first', with the optional filters named inline. It explicitly routes per-token/pool/wallet queries to get_recent_trades, so an agent can distinguish it from that sibling without reading either schema.

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

Usage Guidelines4/5

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

Names the alternative (get_recent_trades) and the condition that selects it, plus the two optional narrowing modes (minAda for 'whale trades', single DEX). It does not state exclusions, such as whether unsettled/pending swaps are excluded or how window interacts with cursor paging.

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

All Realtap tools Inspect

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

Need Help?