MCP Paradex Server

Overview Schema Source Related Servers Score Discussions Admin

paradex_system_config

Check fee schedules, trading limits, and global parameters to understand how the exchange operates and make informed trading decisions.

Instructions

Understand the exchange's global parameters that affect all trading activity.

Use this tool when you need to:
- Check fee schedules before placing trades
- Verify trading limits and restrictions
- Understand exchange-wide parameters that affect your trading
- Keep up with changes to the exchange's configuration

This information provides important context for making trading decisions and
understanding how the exchange operates.

Example use cases:
- Checking current fee tiers for different markets
- Verifying maximum leverage available for specific markets
- Understanding global trading limits or restrictions
- Checking if any exchange-wide changes might affect your trading strategy

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`l1_chain_id`	Yes
`bridged_tokens`	Yes
`oracle_address`	Yes
`liquidation_fee`	Yes
`paraclear_address`	Yes
`starknet_chain_id`	Yes
`block_explorer_url`	Yes
`paraclear_decimals`	Yes
`l1_operator_address`	Yes
`starknet_gateway_url`	Yes
`paraclear_account_hash`	Yes
`l1_core_contract_address`	Yes
`starknet_fullnode_rpc_url`	Yes
`paraclear_account_proxy_hash`	Yes

Implementation Reference

src/mcp_paradex/tools/system.py:22-49 (handler)

The handler function for the 'paradex_system_config' tool. It retrieves the system configuration from the Paradex API using a client, parses the response with SystemConfigSchema, and returns a SystemConfig object. Includes comprehensive documentation on usage.

@server.tool(name="paradex_system_config")
async def get_system_config(ctx: Context) -> SystemConfig:
    """
    Understand the exchange's global parameters that affect all trading activity.

    Use this tool when you need to:
    - Check fee schedules before placing trades
    - Verify trading limits and restrictions
    - Understand exchange-wide parameters that affect your trading
    - Keep up with changes to the exchange's configuration

    This information provides important context for making trading decisions and
    understanding how the exchange operates.

    Example use cases:
    - Checking current fee tiers for different markets
    - Verifying maximum leverage available for specific markets
    - Understanding global trading limits or restrictions
    - Checking if any exchange-wide changes might affect your trading strategy
    """
    try:
        client = await get_paradex_client()
        response = await api_call(client, "system/config")
        system_config = SystemConfigSchema().load(response, unknown="exclude", partial=True)
        return system_config
    except Exception as e:
        await ctx.error(f"Error fetching system configuration: {e!s}")
        raise e

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Jan 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "BridgedToken": {
+      "properties": {
+        "decimals": {
+          "title": "Decimals",
+          "type": "integer"
+        },
+        "l1_bridge_address": {
+          "title": "L1 Bridge Address",
+          "type": "string"
+        },
+        "l1_token_address": {
+          "title": "L1 Token Address",
+          "type": "string"
+        },
+        "l2_bridge_address": {
+          "title": "L2 Bridge Address",
+          "type": "string"
+        },
+        "l2_token_address": {
+          "title": "L2 Token Address",
+          "type": "string"
+        },
+        "name": {
+          "title": "Name",
+          "type": "string"
+        },
+        "symbol": {
+          "title": "Symbol",
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "symbol",
+        "decimals",
+        "l1_token_address",
+        "l1_bridge_address",
+        "l2_token_address",
+        "l2_bridge_address"
+      ],
+      "title": "BridgedToken",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "block_explorer_url": {
+      "title": "Block Explorer Url",
+      "type": "string"
+    },
+    "bridged_tokens": {
+      "items": {
+        "$ref": "#/$defs/BridgedToken"
+      },
+      "title": "Bridged Tokens",
+      "type": "array"
+    },
+    "l1_chain_id": {
+      "title": "L1 Chain Id",
+      "type": "string"
+    },
+    "l1_core_contract_address": {
+      "title": "L1 Core Contract Address",
+      "type": "string"
+    },
+    "l1_operator_address": {
+      "title": "L1 Operator Address",
+      "type": "string"
+    },
+    "liquidation_fee": {
+      "title": "Liquidation Fee",
+      "type": "string"
+    },
+    "oracle_address": {
+      "title": "Oracle Address",
+      "type": "string"
+    },
+    "paraclear_account_hash": {
+      "title": "Paraclear Account Hash",
+      "type": "string"
+    },
+    "paraclear_account_proxy_hash": {
+      "title": "Paraclear Account Proxy Hash",
+      "type": "string"
+    },
+    "paraclear_address": {
+      "title": "Paraclear Address",
+      "type": "string"
+    },
+    "paraclear_decimals": {
+      "title": "Paraclear Decimals",
+      "type": "integer"
+    },
+    "starknet_chain_id": {
+      "title": "Starknet Chain Id",
+      "type": "string"
+    },
+    "starknet_fullnode_rpc_url": {
+      "title": "Starknet Fullnode Rpc Url",
+      "type": "string"
+    },
+    "starknet_gateway_url": {
+      "title": "Starknet Gateway Url",
+      "type": "string"
+    }
+  },
+  "required": [
+    "starknet_gateway_url",
+    "starknet_fullnode_rpc_url",
+    "starknet_chain_id",
+    "block_explorer_url",
+    "paraclear_address",
+    "paraclear_decimals",
+    "paraclear_account_proxy_hash",
+    "paraclear_account_hash",
+    "oracle_address",
+    "bridged_tokens",
+    "l1_core_contract_address",
+    "l1_operator_address",
+    "l1_chain_id",
+    "liquidation_fee"
+  ],
+  "title": "SystemConfig",
+  "type": "object"
+}

First observedAug 15, 2025

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It effectively communicates this is a read-only informational tool (implied by 'understand', 'check', 'verify') and provides context about what information is returned. However, it doesn't mention potential limitations like rate limits, authentication requirements, or data freshness.

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 scenarios, importance context, and example use cases. Every sentence adds value without redundancy, and information is front-loaded appropriately.

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?

Given the tool has zero parameters, no annotations, but has an output schema, the description provides good context about what information is returned and when to use it. The example use cases are particularly helpful. A 5 would require more explicit differentiation from sibling tools.

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 the tool's purpose and usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 understanding global parameters affecting all trading activity, with specific examples like fee schedules and trading limits. However, it doesn't explicitly differentiate from sibling tools like paradex_system_state or paradex_filters_model, which might also provide configuration-related information.

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 usage scenarios in a bulleted list, including checking fee schedules, verifying trading limits, understanding exchange-wide parameters, and keeping up with configuration changes. It gives clear context for when to use this tool.

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