Skip to main content
Glama
Habinar

MCP Paradex Server

by Habinar

paradex_account_fills

Analyze executed trades to review trading history, calculate average entry prices, track realized PnL, and verify order execution details for performance evaluation.

Instructions

Analyze your executed trades to evaluate performance and execution quality.

Use this tool when you need to:
- Review your trading history across specific markets
- Calculate your average entry price for multi-fill positions
- Analyze execution quality compared to intended prices
- Track realized PnL from completed trades
- Verify order execution details for reconciliation

Detailed fill information is essential for performance analysis and
understanding how your orders were actually executed.

Example use cases:
- Calculating volume-weighted average price (VWAP) of your entries
- Analyzing execution slippage from your intended prices
- Reviewing trade history for tax or accounting purposes
- Tracking commission costs across different markets
- Identifying which of your strategies produced the best execution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
market_idYesFilter by market ID.
start_unix_msYesStart time in unix milliseconds.
end_unix_msYesEnd time in unix milliseconds.

Implementation Reference

  • The handler function decorated with @server.tool(name="paradex_account_fills"). It fetches fills from the Paradex client for the specified market and time range, validates using fill_adapter (TypeAdapter(list[Fill])), and returns a structured response including description, schema, and results.
    @server.tool(name="paradex_account_fills")
    async def get_account_fills(
        market_id: Annotated[str, Field(description="Filter by market ID.")],
        start_unix_ms: Annotated[int, Field(description="Start time in unix milliseconds.")],
        end_unix_ms: Annotated[int, Field(description="End time in unix milliseconds.")],
        ctx: Context = None,
    ) -> dict:
        """
        Analyze your executed trades to evaluate performance and execution quality.
    
        Use this tool when you need to:
        - Review your trading history across specific markets
        - Calculate your average entry price for multi-fill positions
        - Analyze execution quality compared to intended prices
        - Track realized PnL from completed trades
        - Verify order execution details for reconciliation
    
        Detailed fill information is essential for performance analysis and
        understanding how your orders were actually executed.
    
        Example use cases:
        - Calculating volume-weighted average price (VWAP) of your entries
        - Analyzing execution slippage from your intended prices
        - Reviewing trade history for tax or accounting purposes
        - Tracking commission costs across different markets
        - Identifying which of your strategies produced the best execution
        """
        client = await get_authenticated_paradex_client()
        params = {"market": market_id, "start_at": start_unix_ms, "end_at": end_unix_ms}
        response = client.fetch_fills(params)
        if "error" in response:
            await ctx.error(response)
            raise Exception(response["error"])
        fills = fill_adapter.validate_python(response["results"])
        results = {
            "description": Fill.__doc__.strip() if Fill.__doc__ else None,
            "fields": Fill.model_json_schema(),
            "results": fills,
        }
        return results
  • Pydantic TypeAdapter for list[Fill], used to validate the response data. Fill is imported from mcp_paradex.models.
    fill_adapter = TypeAdapter(list[Fill])
  • The @server.tool decorator registers the get_account_fills function as the MCP tool named "paradex_account_fills".
    @server.tool(name="paradex_account_fills")
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 is for analysis of executed trades, implying it's a read-only operation (no destructive actions mentioned). However, it lacks details on behavioral traits like rate limits, authentication needs, pagination, or error handling. The description adds some context (e.g., 'Detailed fill information is essential for performance analysis') but doesn't fully compensate for the absence of annotations.

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 a clear opening sentence, bulleted usage guidelines, and example use cases. It is appropriately sized for a tool with three parameters and no annotations, though it could be slightly more concise by integrating some bullet points. Every sentence adds value, such as explaining why fill information is essential, making it front-loaded and efficient.

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 (analysis of executed trades), lack of annotations, and no output schema, the description does a good job of covering purpose and usage. It provides context on what the tool returns (e.g., execution quality, realized PnL) and use cases, compensating for missing structured data. However, it could improve by mentioning output format or limitations, keeping it from a perfect score.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all three parameters (market_id, start_unix_ms, end_unix_ms). The description does not add any parameter-specific semantics beyond what the schema provides (e.g., it doesn't explain format constraints or relationships between parameters). Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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: 'Analyze your executed trades to evaluate performance and execution quality.' It specifies the verb 'analyze' and resource 'executed trades,' distinguishing it from siblings like paradex_account_positions (current holdings) or paradex_orders_history (order status). The description is specific and avoids tautology.

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 when to use this tool, including 'Review your trading history across specific markets' and 'Calculate your average entry price for multi-fill positions.' It implicitly distinguishes from siblings by focusing on executed trades (e.g., vs. paradex_open_orders for pending orders). The example use cases further clarify context, such as for tax purposes or strategy analysis.

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