Skip to main content
Glama
tradeparadex

Paradex MCP Server

by tradeparadex

Vaults

paradex_vaults
Read-onlyIdempotent

Retrieve comprehensive details for a specific vault or list all vaults with optional filtering using JMESPath expressions to limit results.

Instructions

Get detailed information about a specific vault or all vaults if no address is provided.

Retrieves comprehensive details about a specific vault identified by its address,
including configuration, permissions, and other vault-specific parameters.

Use jmespath_filter to reduce the number of results as much as possible as number of vaults can be large.

You can use JMESPath expressions to filter, sort, or limit the results.
Examples:
- Filter by owner: "[?owner_account=='0x123...']"
- Filter by status: "[?status=='ACTIVE']"
- Find vaults with specific strategy: "[?contains(strategies, 'strategy_id')]"
- Sort by creation date: "sort_by([*], &created_at)"
- Limit to newest vaults: "sort_by([*], &created_at)[-5:]"
- Select specific fields: "[*].{address: address, name: name, kind: kind, status: status}"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vault_addressNoThe address of the vault to get details for or empty string to get all vaults.
jmespath_filterNoJMESPath expression to filter, sort, or limit the results.
limitNoLimit the number of results to the specified number.
offsetNoOffset the results to the specified number.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes
totalYes
limitYes
offsetYes
Behavior4/5

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

Annotations already indicate readOnly and idempotent, so the description builds on that by warning that the number of vaults can be large and recommending JMESPath filtering to manage results. This adds useful behavioral context beyond the 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 front-loads the purpose and then provides structured guidance and examples. It is reasonably concise, though slightly longer than the two-sentence ideal. Every sentence adds value.

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 output schema exists and annotations are provided, the description covers the main use, filtering, and large dataset warning. It does not mention error conditions or differentiate from sibling vault tools, but overall is sufficiently complete.

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?

Schema coverage is 100% with clear parameter descriptions. The description adds value by providing JMESPath filtering examples and usage guidance, enriching the semantics beyond what the schema alone offers.

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 starts with 'Get detailed information about a specific vault or all vaults if no address is provided.' This clearly states the action (get) and resource (vaults), and distinguishes from sibling tools that focus on specific aspects like balance or positions.

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

Usage Guidelines3/5

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

The description advises using jmespath_filter to reduce results and provides examples, but it does not explicitly compare this tool to alternatives (e.g., when to use this vs. other vault-specific tools). No when-not-to-use guidance.

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