Skip to main content
Glama
droyd-ai
by droyd-ai

droyd_open_trade

Open cryptocurrency trading positions with configurable legs including market buys, limit orders, stop losses, take profits, and momentum-based triggers to manage risk and automate strategies.

Instructions

Open a new trading position with flexible leg configurations.

Leg Types & Trigger Interpretation:

  • market_buy - Immediate buy at market price (no trigger needed)

  • limit_order - Buy when price drops by triggerPercent (0.05 = buy at 5% below current)

  • stop_loss - Sell when price drops by triggerPercent (0.10 = sell at 10% below entry)

  • take_profit - Sell when price rises by triggerPercent (0.20 = sell at 20% above entry)

  • quant_buy - Buy when momentum score reaches triggerPercent (e.g., 15)

  • quant_sell - Sell when momentum score reaches triggerPercent (e.g., -10)

Examples:

  • Simple buy: { "project_id": 123, "legs": [{ "type": "market_buy", "amountUSD": 100 }] }

  • With stop loss: { "project_id": 123, "legs": [ { "type": "market_buy", "amountUSD": 100 }, { "type": "stop_loss", "amountUSD": 100, "triggerPercent": 0.15 } ]}

  • Scaled take profits: { "project_id": 123, "legs": [ { "type": "market_buy", "amountUSD": 100 }, { "type": "stop_loss", "amountUSD": 100, "triggerPercent": 0.10 }, { "type": "take_profit", "amountUSD": 50, "triggerPercent": 0.25, "positionPercent": 0.5 }, { "type": "take_profit", "amountUSD": 50, "triggerPercent": 0.50, "positionPercent": 0.5 } ]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoProject ID to trade (use this OR contract_address)
contract_addressNoContract address to trade (use this OR project_id)
chainNoBlockchain (required if using contract_address)solana
legsYesTrade legs (1-10)
rationaleNoRationale for the trade
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 explains key traits: it's a creation tool (opening a position), details trigger interpretations for each leg type (e.g., market_buy is immediate, stop_loss sells at a drop), and includes practical constraints like minimum amountUSD in examples. However, it lacks information on permissions, rate limits, or error handling.

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 well-structured and front-loaded with the core purpose, followed by detailed leg type explanations and practical examples. Every sentence earns its place by providing essential context or clarification, with no redundant or verbose content.

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 complexity (trading with multiple leg types), no annotations, and no output schema, the description does a strong job by detailing leg behaviors and providing examples. However, it could improve by mentioning potential outputs or error cases, leaving some gaps for a tool of this complexity.

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 description coverage is 100%, so the baseline is 3. The description adds significant value by explaining the semantics of leg types and triggerPercent with concrete examples (e.g., '0.05 = buy at 5% below current'), clarifying how parameters interact in real-world scenarios beyond the schema's basic descriptions.

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 'Open a new trading position with flexible leg configurations,' which is a specific verb ('open') + resource ('trading position') + distinguishing feature ('flexible leg configurations'). It differentiates from sibling tools like droyd_get_positions (which retrieves) and droyd_manage_trade (which modifies existing trades).

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 implies usage through examples showing when to use different leg types (e.g., 'Simple buy' vs. 'With stop loss'), but it does not explicitly state when to use this tool versus alternatives like droyd_manage_trade or provide exclusions. The guidance is contextual but not comprehensive.

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/droyd-ai/droyd-mcp-server'

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