Skip to main content
Glama
tradeparadex

Paradex MCP Server

by tradeparadex

Market Summaries

paradex_market_summaries
Read-onlyIdempotent

Retrieve current market summaries including mark price, bid/ask, volume, price change, funding rate, and open interest to analyze market conditions and identify trading opportunities.

Instructions

Identify the most active or volatile markets and get current market conditions.

Use this tool when you need to:
- Find the most active markets by volume for liquidity analysis
- Discover markets with significant price movements for momentum strategies
- Compare current prices across multiple assets
- Identify markets with unusual behavior for potential opportunities
- Get the best bid/ask (BBO) for a market — the summary includes bid and ask fields
- Get the current funding rate — the summary includes funding_rate

Retrieves current market summary information including mark price, best bid/ask,
last traded price, 24h volume and price change, funding rate, open interest, and
underlying spot price. If "ALL" is specified or no market IDs are provided,
returns summaries for all available markets.

Prefer this tool over separate paradex_bbo or paradex_funding_data calls when you
need price context before making a trading recommendation — all that data is here.

Example use cases:
- Finding high-volatility markets for short-term trading
- Identifying top gainers and losers for the day
- Comparing volume across different markets to find liquidity
- Getting the current price and 24-hour range for price analysis
- Checking bid/ask spread and funding rate before placing an order

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 high price: "[?high_price > `10000`]"
- Sort by volume: "sort_by([*], &volume)"
- Get top 3 by price change: "[sort_by([*], &to_number(price_change_percent))[-3:]]"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
market_idsNoMarket symbols to get summaries 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
Behavior5/5

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

Annotations declare readOnlyHint and idempotentHint true. The description reinforces read-only nature and adds detail: returns all markets if 'ALL' or no IDs, supports JMESPath filtering, and includes limit/offset. No contradiction.

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?

Structure is clear with bullet points and examples, front-loading purpose and use cases. Slightly verbose but each sentence adds value; no redundant fluff.

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?

Given 4 parameters, full schema coverage, and output schema exists, the description is remarkably complete. It covers behavior with 'ALL', JMESPath filtering, typical use cases, and data fields included.

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% with descriptions. The description adds value by explaining default behavior for market_ids, demonstrating JMESPath expressions, and clarifying limit/offset usage. Examples enrich understanding beyond 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's purpose: 'Identify the most active or volatile markets and get current market conditions.' It lists specific use cases and distinguishes from sibling tools like paradex_bbo and paradex_funding_data by advising preference when price context is needed.

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?

Explicitly lists when to use (e.g., finding active markets, comparing prices, getting BBO/funding rate) and provides examples. Does not explicitly state when not to use, but gives strong contextual guidance.

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