Skip to main content
Glama

execute_limit_order

Sign and submit a pre-built limit order transaction on Solana to place an order that executes automatically when market conditions are met. Returns the transaction signature upon success.

Instructions

🚨 WARNING: THIS WILL CREATE A REAL LIMIT ORDER ON-CHAIN! 🚨

Sign and execute a limit order transaction.

This is a PAID operation that creates a limit order on the Solana blockchain. The order will execute automatically when market conditions are met.

Args: transaction: Base64 encoded unsigned transaction from create_limit_order request_id: Request ID from create_limit_order response

Returns: Dictionary containing: - success: Boolean indicating if the execution was successful - data: Contains 'signature' and status if successful - error: Error message if execution failed

Note: - This creates a limit order that may execute later - Orders have fees: 0.03% (stable pairs) or 0.1% (other pairs) - Plus automatic referral fees (2.55%) - Minimum order size is $5 USD

Example: >>> # First create the order >>> order = await api.create_limit_order(...) >>> if order["success"]: ... # Then execute it ... result = await api.execute_limit_order( ... transaction=order["data"]["transaction"], ... request_id=order["data"]["requestId"] ... ) ... if result["success"]: ... print(f"Limit order created! Signature: {result['data']['signature']}")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_idYes
transactionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses the paid nature, on-chain execution, automatic order matching, fees, minimum order size, and return structure. It also warns about creating a real order, giving the agent a clear safety profile.

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 a warning, summary, args, returns, notes, and example. It is longer than minimal but every section adds value; the example is practical. The attention-grabbing warning is slightly theatrical but not wasteful.

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

Completeness5/5

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

The description covers purpose, inputs, outputs, fees, execution behavior, and workflow, making it complete for a two-parameter tool. The presence of an output schema is supplemented by the detailed return description, so nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explicitly explains both parameters: transaction is 'Base64 encoded unsigned transaction from create_limit_order' and request_id is 'Request ID from create_limit_order response'. This adds meaning far beyond the schema's bare string definitions.

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 'Sign and execute a limit order transaction' and specifies it creates a limit order on Solana. It distinguishes from siblings like execute_swap_transaction by emphasizing limit order and by referencing create_limit_order as the source of inputs.

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: it is a paid operation used after create_limit_order, with an example illustrating the create-then-execute workflow. It does not explicitly mention alternatives or when not to use, but the context is sufficient for an agent to select it appropriately.

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/araa47/jupiter-mcp'

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