Skip to main content
Glama
Habinar

MCP Paradex Server

by Habinar

paradex_vault_transfers

Track deposit and withdrawal history for auditing and reconciliation. Verify transaction status, monitor fund flows, and maintain clear audit trails for vault capital movements.

Instructions

Track deposit and withdrawal history for auditing and reconciliation.

Use this tool when you need to:
- Verify deposits have completed and are available for trading
- Track withdrawal status and confirm transaction settlement
- Audit the complete fund flow history for a vault
- Reconcile on-chain transactions with platform records
- Understand historical capital allocation patterns

Complete transfer history is essential for proper accounting and provides
a clear audit trail of all capital movements.

Example use cases:
- Confirming that a recent deposit was credited to your account
- Tracking the status of pending withdrawals
- Creating transaction reports for accounting or tax purposes
- Verifying the total amount deposited over time
- Analyzing deposit/withdrawal patterns for strategy insights

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vault_addressYesThe address of the vault to get transfers for.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'paradex_vault_transfers' tool. It takes a vault_address parameter and fetches the transfer history from the Paradex API using api_call to 'vaults/transfers'. Returns the results or an error dict on failure.
    @server.tool(name="paradex_vault_transfers")
    async def get_vault_transfers(
        vault_address: Annotated[
            str, Field(description="The address of the vault to get transfers for.")
        ],
    ) -> dict[str, Any]:
        """
        Track deposit and withdrawal history for auditing and reconciliation.
    
        Use this tool when you need to:
        - Verify deposits have completed and are available for trading
        - Track withdrawal status and confirm transaction settlement
        - Audit the complete fund flow history for a vault
        - Reconcile on-chain transactions with platform records
        - Understand historical capital allocation patterns
    
        Complete transfer history is essential for proper accounting and provides
        a clear audit trail of all capital movements.
    
        Example use cases:
        - Confirming that a recent deposit was credited to your account
        - Tracking the status of pending withdrawals
        - Creating transaction reports for accounting or tax purposes
        - Verifying the total amount deposited over time
        - Analyzing deposit/withdrawal patterns for strategy insights
        """
        try:
            client = await get_paradex_client()
            response = await api_call(client, "vaults/transfers", params={"address": vault_address})
            return response["results"]
        except Exception as e:
            logger.error(f"Error fetching transfers for vault {vault_address}: {e!s}")
            return {
                "success": False,
                "timestamp": datetime.now().isoformat(),
                "environment": config.ENVIRONMENT,
                "error": str(e),
                "transfers": None,
            }
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 describes the tool's function as tracking history for auditing, implying it's a read-only operation, but doesn't explicitly state behavioral traits like whether it requires authentication, has rate limits, or details on data freshness. It adds some context (e.g., 'complete transfer history') but lacks specifics on performance or constraints.

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's appropriately sized and front-loaded, though it could be slightly more concise by avoiding repetition between guidelines and examples. Every sentence adds value, but there's minor redundancy.

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 (read-only history tracking), no annotations, and an output schema exists (implying return values are documented), the description is fairly complete. It covers purpose, usage, and examples, but could improve by addressing behavioral aspects like data latency or access permissions to fully compensate for the lack of annotations.

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?

The input schema has 100% description coverage, with the parameter 'vault_address' clearly documented. The description doesn't add any meaning beyond what the schema provides, as it doesn't explain the parameter's role or format. With high schema coverage, the baseline is 3, and the description doesn't compensate with additional insights.

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 tracking deposit and withdrawal history for auditing and reconciliation, which is a specific verb+resource combination. However, it doesn't explicitly distinguish this from sibling tools like 'paradex_account_transactions' or 'paradex_vault_account_summary', which might have overlapping functionality, so it misses full sibling differentiation.

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 (e.g., verify deposits, track withdrawal status, audit fund flow, reconcile transactions, understand patterns). It clearly outlines specific scenarios, though it doesn't explicitly mention when not to use it or name alternatives among siblings.

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