Paradex MCP Server

Candlestick Data

paradex_klines

Read-onlyIdempotent

Retrieve historical candlestick data for technical analysis, enabling calculation of indicators like moving averages, RSI, and MACD for trading decisions.

Instructions

Analyze historical price patterns for technical analysis and trading decisions.

Use this tool when you need to:
- Perform technical analysis on historical price data
- Identify support and resistance levels from price history
- Calculate indicators like moving averages, RSI, or MACD
- Backtest trading strategies on historical data
- Visualize price action over specific timeframes

Candlestick data is fundamental for most technical analysis and trading decisions,
providing structured price and volume information over time.

Example use cases:
- Identifying chart patterns for potential entries or exits
- Calculating technical indicators for trading signals
- Determining volatility by analyzing price ranges
- Finding significant price levels from historical support/resistance
- Measuring volume patterns to confirm price movements

Input Schema

TableJSON Schema

Name	Required	Description
`market_id`	Yes	Market symbol to get klines for.
`resolution`	No	The time resolution of the klines.
`start_unix_ms`	Yes	Start time in unix milliseconds.
`end_unix_ms`	Yes	End time in unix milliseconds.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Tool Definition Quality

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds value by explaining the data is historical, structured, and used for technical analysis, without contradicting annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections but somewhat verbose; some repetition (e.g., 'technical analysis' appears multiple times). Could be trimmed while retaining key information.

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 an output schema present, the description adequately covers usage, examples, and context. Does not detail return fields, which is acceptable given output schema availability.

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% with clear parameter descriptions. The description does not add further parameter-level detail beyond the schema, so it meets baseline but doesn't exceed.

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?

Description clearly states the tool provides historical candlestick data for technical analysis, with a specific verb 'analyze' and resource 'historical price patterns'. It distinguishes from sibling tools like paradex_bbo (real-time BBO) and paradex_orderbook (order book) by emphasizing historical analysis.

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?

Provides explicit bullet list of when to use the tool and example use cases. Lacks explicit when-not-to-use or alternatives, but the list implicitly guides appropriate usage.

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

Install Server

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

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