Skip to main content
Glama
nexus-xyz

nexus-exchange-mcp

Official
by nexus-xyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_trades

Fetch recent public trades for one market, newest first, with cursor-based pagination. Deprecated: use fetch_trades instead; no credentials needed.

Instructions

Deprecated: use fetch_trades. Get recent public trades (prints) for one market, newest first. Returns { items, next_cursor }. items is this page of results; next_cursor is an opaque token for the next page, or null when this is the last page. To read the full history, keep calling with cursor: <previous next_cursor> until next_cursor is null. limit sets the size of ONE page, not a total. Public — no credentials needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of trades per page (max 1000).
cursorNoOpaque pagination cursor. Omit for the first page; to get the next page, pass back the `next_cursor` from the previous response verbatim. Stop when `next_cursor` is null — that means there are no more results. Never construct or edit a cursor: the format is not part of the contract.
market_idYesMarket id, e.g. "BTC-USDX-PERP".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque pagination cursor. Omit for the first page; to get the next page, pass back the `next_cursor` from the previous response verbatim. Stop when `next_cursor` is null — that means there are no more results. Never construct or edit a cursor: the format is not part of the contract.",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of trades to return."New value: +"Maximum number of trades per page (max 1000)."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it declares the access profile ("Public — no credentials needed"), the ordering guarantee (newest first), the pagination contract (`next_cursor` opaque, null terminates), and clarifies that `limit` is per-page rather than a total. This is exactly the behavioral context annotations would otherwise need to supply.

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?

Front-loads the deprecation warning, then purpose, then return shape and pagination in a logical order. It is somewhat long and repeats the cursor story that the schema already tells, but every sentence still earns its place for a paging tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description supplies the return shape (`{ items, next_cursor }`), the token semantics, and the termination condition, plus auth requirements. Nothing needed to call this tool correctly 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 100%, so baseline is 3, but the description adds a genuinely useful disambiguation by stating "`limit` sets the size of ONE page, not a total" and explaining the cursor round-trip. Most cursor text mirrors the schema, keeping it below a 5.

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?

States a specific verb and resource ("Get recent public trades (prints) for one market, newest first") and immediately flags itself as deprecated in favor of a named sibling (`fetch_trades`). An agent can distinguish it from `get_orderbook`, `get_candles`, and `fetch_my_trades` without opening a schema.

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

Usage Guidelines5/5

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

Explicitly says when NOT to use it ("Deprecated: use `fetch_trades`") and then explains exactly how to consume it (loop on `cursor` until `next_cursor` is null). Both the alternative and the operative condition are named, with nothing left to inference.

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

Deploy Server

Other Tools