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")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "Model representing the current state of the Paradex system.",
      +  "properties": {
      +    "status": {
      +      "title": "Status",
      +      "type": "string"
      +    },
      +    "timestamp": {
      +      "default": 0,
      +      "title": "Timestamp",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "status"
      +  ],
      +  "title": "SystemState",
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by describing the tool's purpose (verification/checking), context (operational status, maintenance periods, clock sync), and importance (critical trades, API issue diagnosis). It doesn't mention rate limits, authentication needs, or specific error conditions, but provides substantial behavioral context.

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 with clear sections (purpose statement, usage bullet points, importance context, example use cases). Every sentence adds value without redundancy, and the information is front-loaded with the core purpose stated first.

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, output schema exists), the description provides comprehensive context about when and why to use this tool. It covers purpose, usage scenarios, importance, and examples, which is complete for a status-checking tool with no parameters.

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 zero parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on usage context and scenarios.

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 with specific verbs ('verify', 'check', 'confirm') and identifies the resource ('exchange', 'Paradex'). It distinguishes from siblings by focusing on system operational status rather than trading, account, or market data functions.

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 when-to-use guidance with bullet points listing specific scenarios (before trades, during unexpected behavior, before maintenance checks, for clock sync). It also includes 'especially important' context and example use cases that reinforce appropriate usage contexts.

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