Skip to main content
Glama
tradeparadex

Paradex MCP Server

by tradeparadex

Funding Payments

paradex_account_funding_payments
Read-onlyIdempotent

Track funding payment history to calculate costs or gains for positions, analyze effect on overall performance, and plan position timing around payment schedules.

Instructions

Track your funding payment history to understand its impact on P&L.

Use this tool when you need to:
- Calculate total funding costs or gains for a position
- Analyze how funding has affected your overall performance
- Plan position timing around funding payment schedules
- Compare funding costs across different markets
- Account for funding in your trading strategy profitability

Funding payments can significantly impact trading P&L,
especially for longer-term positions or in markets with volatile funding rates.

Example use cases:
- Calculating the total funding component of your P&L
- Comparing funding costs against trading profits
- Planning position entries/exits around funding payment times
- Identifying markets where funding has been consistently favorable
- Reconciling funding payments for accounting purposes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
market_idNoFilter by market ID.
start_unix_msYesStart time in unix milliseconds.
end_unix_msYesEnd time in unix milliseconds.
Behavior3/5

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

Annotations already indicate readOnlyHint and idempotentHint. The description adds context about the impact of funding payments on P&L, which is useful but not critical. It does not disclose pagination, rate limits, or output format, which would be needed for full transparency.

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 bullet points and examples, making it easy to scan. It is front-loaded with the main purpose. However, a few sentences are somewhat repetitive (e.g., 'Funding payments can significantly impact trading P&L') and could be slightly more concise.

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 simplicity (3 parameters, no output schema, read-only), the description is fairly complete. It explains what the tool does, when to use it, and provides use cases. However, it does not describe the response format or any limitations like historical depth, which would improve completeness.

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, so the parameters are already well-documented. The description does not add significant meaning beyond the schema; it mentions 'position timing' but that is more about usage than parameter semantics. Baseline 3 is appropriate.

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 title 'Funding Payments' and description clearly state it tracks funding payment history for a specific account. It distinguishes from sibling tools like paradex_funding_data (market-wide rates) by focusing on account-level impact on P&L. The verb 'track' and resource 'funding payment history' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly lists five scenarios for using the tool (e.g., calculating total funding costs, planning position timing) and provides example use cases. However, it does not explicitly contrast with alternatives like paradex_funding_data for market-level data, leaving some ambiguity.

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/tradeparadex/mcp-paradex-py'

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