Skip to main content
Glama
Habinar

MCP Paradex Server

by Habinar

paradex_system_state

Check if Paradex exchange is operational before trading by verifying system status, maintenance periods, and clock synchronization.

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 handler function decorated with @server.tool(name="paradex_system_state"), which fetches the Paradex system state and time using the client and returns 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
  • Pydantic BaseModel defining the output structure for the paradex_system_state 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 @server.tool decorator registers the paradex_system_state tool with the MCP server.
    @server.tool(name="paradex_system_state")
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's purpose as a read-only status check (implied by 'verify' and 'check'), highlights its importance for safety before trades, and mentions context like maintenance periods and clock sync. However, it doesn't specify rate limits, authentication needs, or exact response format, leaving some behavioral aspects uncovered.

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

Conciseness5/5

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

The description is well-structured and front-loaded with a clear purpose statement, followed by bullet points and examples. Every sentence adds value by elaborating on usage scenarios without redundancy. It efficiently conveys necessary information in a compact format.

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 the tool's simplicity (0 parameters, no annotations, but with an output schema), the description is complete. It explains the tool's purpose, usage guidelines, and importance in trading contexts. The output schema will handle return values, so the description doesn't need to detail them, making it sufficiently comprehensive for this low-complexity tool.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description adds no parameter-specific information, which is appropriate here. A baseline of 4 is applied for zero-parameter tools, as no additional semantic value is needed beyond the schema's completeness.

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 as verifying exchange operational status before trades, using specific verbs like 'verify' and 'check' with the resource 'exchange' or 'system status'. It distinguishes from sibling tools (e.g., trading or account tools) by focusing on system health rather than market data or account actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool: before executing important orders, when encountering unexpected behavior, to check maintenance periods, and for clock synchronization. It includes specific use cases (e.g., before trading strategies, during market volatility) and implies alternatives by suggesting it for diagnosing API issues when other calls fail.

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

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