Skip to main content
Glama
tradeparadex

Paradex MCP Server

by tradeparadex

Generate Subkey

paradex_generate_subkey

Generate a Paradex subkey keypair locally, keeping the private key secure, and output the public key for agent trading registration.

Instructions

Generate a Paradex keypair for use as a subkey.

The private key is persisted locally and never leaves the machine.
Only the public key is returned so the frontend can register it on
Paradex on behalf of the agent.

Use this tool when you need to:
- Provision a new subkey for agent trading
- Create a keypair before registering the public key on Paradex

Example use cases:
- Setting up a new agent with its own trading subkey
- Rotating to a fresh subkey for an existing account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional label for the key. Must contain only alphanumeric characters, hyphens, or underscores. If omitted, a default name is generated from the current timestamp.
pathNoOptional absolute directory path where the key file will be stored. If omitted, defaults to ~/.mcp-paradex/keys/. The directory must exist and be writable.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesLabel for the generated key
public_keyYesParadex public key in hex format (0x...)
Behavior5/5

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

The description adds significant behavioral context beyond annotations: private key is persisted locally and never leaves the machine, only public key is returned. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, well-structured with bullets, and every sentence adds value. It is front-loaded with the main action and avoids unnecessary details.

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?

The description covers key behavioral aspects and provides context about registration on Paradex as a next step. Given that an output schema exists, it is very complete, though it does not address duplicate keys or error scenarios.

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 coverage is 100%, and both parameters are already described in the schema. The description does not add extra parameter information, so baseline score of 3 applies.

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 explicitly states it generates a Paradex keypair as a subkey, explains where the private key stays and what is returned, and is clearly differentiated from sibling tools as no other tool generates keys.

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 lists specific use cases and example scenarios, but does not explicitly state when NOT to use the tool or mention alternatives. However, the context is clear and no competing sibling tools exist.

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