paradex_system_state
Check Paradex system status to verify exchange functionality before executing trades. Use to diagnose API issues, confirm maintenance status, and ensure clock synchronization for optimal trading.
Instructions
Verify the exchange is fully operational before executing trades.
Use this tool when you need to:
- Check if Paradex is functioning normally before placing important orders
- Verify system status if you encounter unexpected behavior
- Confirm that maintenance periods are not in effect
- Check exchange clock synchronization with your own systems
This is especially important before executing critical trades or when
experiencing unexpected behavior from other API calls.
Example use cases:
- Verifying the exchange is operational before executing a trading strategy
- Checking if maintenance mode is active when experiencing delays
- Confirming exchange status during periods of market volatility
- Diagnosing API issues by checking system health
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Implementation Reference
- src/mcp_paradex/tools/system.py:52-79 (handler)Handler function decorated with @server.tool(name="paradex_system_state"), implementing the tool logic by fetching system state and server time from Paradex client and constructing a SystemState object.@server.tool(name="paradex_system_state") async def get_system_state(ctx: Context) -> SystemState: """ Verify the exchange is fully operational before executing trades. Use this tool when you need to: - Check if Paradex is functioning normally before placing important orders - Verify system status if you encounter unexpected behavior - Confirm that maintenance periods are not in effect - Check exchange clock synchronization with your own systems This is especially important before executing critical trades or when experiencing unexpected behavior from other API calls. Example use cases: - Verifying the exchange is operational before executing a trading strategy - Checking if maintenance mode is active when experiencing delays - Confirming exchange status during periods of market volatility - Diagnosing API issues by checking system health """ try: client = await get_paradex_client() state = client.fetch_system_state() time = client.fetch_system_time() return SystemState(status=state["status"], timestamp=time["server_time"]) except Exception as e: await ctx.error(f"Error fetching system state: {e!s}") raise e
- src/mcp_paradex/models.py:15-20 (schema)Pydantic BaseModel defining the output structure for the paradex_system_state tool: status (str) and timestamp (int). Used as return type annotation and instantiation in the handler.class SystemState(BaseModel): """Model representing the current state of the Paradex system.""" status: str timestamp: int = Field(default=0)
- src/mcp_paradex/tools/system.py:52-52 (registration)The @server.tool decorator registers the get_system_state function as the MCP tool named "paradex_system_state".@server.tool(name="paradex_system_state")