jupiter_createLimitOrder
InactiveTool of SAP MCP Server
Create a limit order. Returns an unsigned transaction — sign and submit via executeTrigger. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy.
Parameters schema
{
"type": "object",
"required": [
"maker",
"payer",
"inputMint",
"outputMint",
"makingAmount",
"takingAmount"
],
"properties": {
"maker": {
"type": "string",
"description": "Wallet address of the order creator"
},
"payer": {
"type": "string",
"description": "Wallet paying for transaction fees"
},
"feeBps": {
"type": "number",
"description": "Referral fee in bps"
},
"expiredAt": {
"type": "string",
"description": "ISO 8601 expiry timestamp"
},
"inputMint": {
"type": "string",
"description": "Input token mint"
},
"outputMint": {
"type": "string",
"description": "Output token mint"
},
"makingAmount": {
"type": "string",
"description": "Amount of input token to sell"
},
"takingAmount": {
"type": "string",
"description": "Amount of output token to receive"
},
"computeUnitPrice": {
"type": "string",
"description": "Priority fee (µ-lamports/CU)"
}
},
"additionalProperties": false
}No endpoints wrapped at confidence ≥ 0.50.
Parent server
SAP MCP Server
https://github.com/OOBE-PROTOCOL/sap-mcp
2/7 registries