Skip to main content
Glama
Habinar

MCP Paradex Server

by Habinar

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
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
l1_chain_idYes
bridged_tokensYes
oracle_addressYes
liquidation_feeYes
paraclear_addressYes
starknet_chain_idYes
block_explorer_urlYes
paraclear_decimalsYes
l1_operator_addressYes
starknet_gateway_urlYes
paraclear_account_hashYes
l1_core_contract_addressYes
starknet_fullnode_rpc_urlYes
paraclear_account_proxy_hashYes

Implementation Reference

  • 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
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool provides 'important context for making trading decisions' and helps 'keep up with changes,' implying it's a read-only, informational tool without side effects. However, it lacks details on behavioral traits such as rate limits, authentication requirements, or data freshness, which are important for a trading context.

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

Conciseness4/5

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

The description is well-structured with clear sections: purpose, usage guidelines, and example use cases. It's appropriately sized and front-loaded, starting with the core purpose. However, some sentences in the example use cases could be more concise, and the overall length is moderate but not excessive.

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's complexity (informational with 0 parameters), no annotations, and the presence of an output schema, the description is fairly complete. It explains the tool's role in trading decisions and provides usage examples, but it could benefit from more detail on output format or limitations, though the output schema mitigates this gap.

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, and schema description coverage is 100%, so there's no need for parameter semantics in the description. The baseline for 0 parameters is 4, as the description doesn't need to compensate for any missing parameter info, and it appropriately focuses on usage and context without redundant details.

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: 'Understand the exchange's global parameters that affect all trading activity.' It specifies the verb 'understand' and resource 'global parameters,' making the intent explicit. However, it doesn't distinctly differentiate from sibling tools like 'paradex_system_state' or 'paradex_filters_model,' which might also relate to system-wide information, so it falls short of a perfect score.

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 guidelines with a bulleted list of scenarios: 'Check fee schedules before placing trades,' 'Verify trading limits and restrictions,' etc. It clearly indicates when to use this tool by linking it to specific needs like understanding exchange-wide parameters and making trading decisions, though it doesn't explicitly mention when not to use it or name alternatives.

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