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

droyd_manage_trade

Manage existing cryptocurrency trading positions by closing, adding buys, executing partial sells, or modifying strategy legs like stop losses and take profits.

Instructions

Manage existing trading positions. Close positions, execute additional buys/sells, or modify strategy legs.

Actions:

  • close - Exit entire position at market

  • buy - Add to existing position (requires amountUSD)

  • sell - Partial exit (requires sellPercent, e.g., 0.5 = sell 50%)

  • update - Modify stop losses and take profits

Examples:

  • Close position: { "strategy_id": 789, "action": "close" }

  • Partial sell: { "strategy_id": 789, "action": "sell", "sellPercent": 0.25 }

  • Add buy: { "strategy_id": 789, "action": "buy", "amountUSD": 50 }

  • Add stop loss: { "strategy_id": 789, "action": "update", "legs": [ { "leg_action": "add", "type": "stop_loss", "amountUSD": 100, "triggerPercent": 0.10 } ]}

  • Update existing leg: { "strategy_id": 789, "action": "update", "legs": [ { "leg_action": "update", "leg_id": 123, "triggerPercent": 0.15 } ]}

  • Remove leg: { "strategy_id": 789, "action": "update", "legs": [ { "leg_action": "remove", "leg_id": 456 } ]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
strategy_idYesStrategy ID to manage
actionYesAction to perform
amountUSDNoAmount in USD (required for buy action)
portfolio_percentNoPortfolio percent for buy (0-100)
sellPercentNoPortion to sell 0-1 (required for sell action)
project_idNoOverride project for buy/sell
legsNoLeg modifications (required for update action)
Behavior3/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 does well by explaining the different actions (close, buy, sell, update) and their effects. However, it doesn't mention important behavioral aspects like whether these actions are reversible, what permissions are required, rate limits, or what happens to partially executed orders. The examples help but don't cover all behavioral implications.

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 clear sections (Actions, Examples) and uses bullet points effectively. The opening sentence clearly states the purpose. While comprehensive, some sentences could be more concise, and the examples section is quite lengthy but necessary for this complex tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex trading tool with 7 parameters, no annotations, and no output schema, the description does a decent job but has gaps. It explains the actions well with examples, but doesn't cover error conditions, return values, or system limitations. Given the complexity and financial nature of the operations, more context about what happens after execution would be helpful.

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 beyond the schema by explaining the semantic meaning of each action type with clear examples. It clarifies what 'close', 'buy', 'sell', and 'update' mean in practice, and provides concrete examples of how to use the legs parameter for different leg actions. This goes well beyond what the schema provides.

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 with specific verbs and resources: 'Manage existing trading positions. Close positions, execute additional buys/sells, or modify strategy legs.' It distinguishes this tool from siblings like droyd_open_trade (which opens new trades) and droyd_get_positions (which retrieves positions without modifying them). The description provides a comprehensive overview of all possible actions.

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 provides clear context for when to use this tool: for managing existing trading positions. It implicitly distinguishes from droyd_open_trade (for opening new trades) and droyd_get_positions (for retrieving position information). However, it doesn't explicitly state when NOT to use this tool or provide specific alternatives for edge cases.

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