Skip to main content
Glama
sv

MCP Paradex Server

by sv

paradex_system_state

Read-only

Verify Paradex exchange system status to confirm it is operational, not in maintenance mode, and clock synchronized before executing trades.

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
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes
timestampNo

Implementation Reference

  • The main handler function for the 'paradex_system_state' tool. It fetches system state (status) and system time from Paradex and returns them as a SystemState model.
    @server.tool(name="paradex_system_state", annotations=ToolAnnotations(readOnlyHint=True))
    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
  • The Pydantic model (SystemState) that defines the output schema for the tool: status (str) and timestamp (int).
    class SystemState(BaseModel):
        """Model representing the current state of the Paradex system."""
    
        status: str
        timestamp: int = Field(default=0)
  • The tool registration via the @server.tool() decorator, binding the name 'paradex_system_state' to the get_system_state handler.
    @server.tool(name="paradex_system_state", annotations=ToolAnnotations(readOnlyHint=True))
  • Test verifying the tool returns correct status and timestamp from the API.
    async def test_system_state_returns_status_and_timestamp(mock_client):
        mock_client.fetch_system_state.return_value = {"status": "ok"}
        mock_client.fetch_system_time.return_value = {"server_time": 1_700_000_000_000}
    
        result = await server.call_tool("paradex_system_state", {})
        data = _json(result)
    
        assert data["status"] == "ok"
        assert data["timestamp"] == 1_700_000_000_000
        mock_client.fetch_system_state.assert_called_once()
        mock_client.fetch_system_time.assert_called_once()
Behavior4/5

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

ReadOnlyHint already indicates no side effects. Description adds value by detailing what is checked (maintenance, clock sync) and emphasizing importance before critical trades, going beyond annotation.

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?

Fairly organized but slightly verbose with bullet points and examples. Could be trimmed to core sentences without losing meaning.

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?

With no parameters and a simple status check, the description fully covers why and when to use the tool. The existence of an output schema further reduces need for return value details.

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?

No parameters in schema (100% coverage), so description doesn't need to add param info. It still justifies the tool's role, which is sufficient.

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 checks if the exchange is operational, with a specific verb ('verify') and resource ('exchange system state'). It distinguishes itself from sibling tools by focusing on system readiness, not market data or configuration.

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., before trades, on unexpected behavior, check maintenance, clock sync). Lacks explicit when-not-to-use or alternatives, but context is clear.

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/sv/mcp-paradex-py'

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