Skip to main content
Glama
tradeparadex

Paradex MCP Server

by tradeparadex

Markets

paradex_markets
Read-onlyIdempotent

Retrieve market specifications including tick size, minimum order size, and base/quote assets for perpetual futures and options markets. Filter by asset or use JMESPath expressions to sort and limit results.

Instructions

Find markets that match your trading criteria or get detailed market specifications.

Use this tool when you need to:
- Understand exact tick sizes and minimum order sizes before placing trades
- Find all markets for a specific asset (e.g., all BTC-based markets)
- Compare contract specifications across different markets
- Identify markets with specific characteristics for your trading strategy

Retrieves comprehensive details about specified markets, including
base and quote assets, tick size, minimum order size, and other
trading parameters. If "ALL" is specified or no market IDs are provided,
returns details for all available markets.

Example use cases:
- Finding the minimum order size for a new trade
- Identifying markets with the smallest tick size for precise entries
- Checking which assets are available for trading

`asset_kind` is the type of asset in the market: `PERP` (perpetual futures),
`PERP_OPTION` (perpetual options), `SPOT` (spot markets), `OPTION` (dated/expiring options),
or `FUTURE` (dated futures).

You can use JMESPath expressions (https://jmespath.org/specification.html) to filter, sort, or limit the results.
Use the `paradex_filters_model` tool to get the filters for a tool.
Examples:
- Filter by base asset: "[?base_asset=='BTC']"
- Sort by 24h volume: "sort_by([*], &volume_24h)"
- Limit to top 5 by volume: "[sort_by([*], &to_number(volume_24h))[-5:]]"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
market_idsNoMarket symbols to get details for.
jmespath_filterNoJMESPath expression to filter, sort, or limit the results.
limitNoLimit the number of results to the specified number.
offsetNoOffset the results to the specified number.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes
totalYes
limitYes
offsetYes
Behavior4/5

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

Annotations already indicate readOnly and idempotent. The description adds context about default behavior when no market IDs are given, how limit/offset work, and that JMESPath filtering is supported. No contradictions with annotations.

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?

The description is well-structured with a clear beginning, bulleted use cases, parameter explanations, and examples. It is slightly verbose but each sentence adds value. The asset_kind paragraph may be marginally misplaced but does not detract.

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?

Given the complexity (JMESPath, filtering, multiple parameters) and presence of an output schema, the description adequately covers purpose, parameters, and usage patterns. It could mention rate limits or result ordering but is otherwise comprehensive.

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

Parameters5/5

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

All parameters have schema descriptions, but the description adds substantial value: explains the 'ALL' default for market_ids, provides JMESPath examples, and clarifies limit/offset usage. This enriches the parameter meaning beyond the schema.

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?

The description clearly states the tool retrieves market specifications and lists specific use cases like finding tick sizes and comparing contracts. It effectively distinguishes from sibling tools by focusing on detailed market data rather than summaries or order books.

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?

The description provides concrete scenarios for when to use the tool (e.g., understanding tick sizes, finding all BTC markets). It references the paradex_filters_model tool but does not explicitly exclude other market tools like paradex_market_summaries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tradeparadex/mcp-paradex-py'

If you have feedback or need assistance with the MCP directory API, please join our Discord server