Skip to main content
Glama
sv

MCP Paradex Server

by sv

paradex_vault_transfers

Track deposit and withdrawal history for auditing and reconciliation, verifying transaction status and analyzing capital movement patterns.

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 decorated with @server.tool for the paradex_vault_transfers tool. It fetches the transfer history for a given vault address via the Paradex API and returns the results or an error response.
    @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,
            }
  • The @server.tool decorator registers the get_vault_transfers function as the MCP tool named paradex_vault_transfers.
    @server.tool(name="paradex_vault_transfers")
  • The function signature defines the input schema using Pydantic Annotated and Field for the vault_address parameter, and returns dict[str, Any] for transfer data.
    async def get_vault_transfers(
        vault_address: Annotated[
            str, Field(description="The address of the vault to get transfers for.")
        ],
    ) -> dict[str, Any]:
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's function as historical tracking for auditing purposes, implying read-only behavior without destructive actions. However, it doesn't specify data format, pagination, or rate limits, leaving some behavioral aspects unclear.

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 purpose statement followed by usage scenarios and example use cases. While slightly verbose, every section adds value by clarifying context and applications. It could be more concise by combining some bullet points, but overall it's efficiently organized.

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 moderate complexity (historical data retrieval), no annotations, and the presence of an output schema (which handles return values), the description provides good contextual completeness. It explains the tool's purpose, usage scenarios, and value proposition, though it could benefit from mentioning data recency or limitations.

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, clearly documenting the single required parameter 'vault_address'. The description doesn't add any additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage.

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 as tracking deposit and withdrawal history for auditing and reconciliation. It specifies the verb 'track' and resource 'deposit and withdrawal history', distinguishing it from sibling tools like paradex_vault_balance (which likely shows current balance) or paradex_account_transactions (which might be for general account activity).

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 guidance on when to use this tool through a bulleted list of scenarios (e.g., verifying deposits, tracking withdrawals, auditing fund flow). It implicitly distinguishes from siblings by focusing on vault-specific transfer history rather than general account data or current balances, though it doesn't explicitly 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/sv/mcp-paradex-py'

If you have feedback or need assistance with the MCP directory API, please join our Discord server