jupiter_getLimitOrders
InactiveTool of SAP MCP Server
Get all limit orders (active and optionally historical) for a wallet. 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": [
"wallet",
"orderStatus"
],
"properties": {
"page": {
"type": "number",
"description": "Page pagination control for Jupiter Get Limit Orders."
},
"limit": {
"type": "number",
"description": "Limit controlling the maximum number of results returned by Jupiter Get Limit Orders."
},
"wallet": {
"type": "string",
"description": "Wallet address to query"
},
"inputMint": {
"type": "string",
"description": "Token mint address (base58)"
},
"outputMint": {
"type": "string",
"description": "Token mint address (base58)"
},
"orderStatus": {
"enum": [
"active",
"history"
],
"type": "string",
"description": "Filter by order status: \"active\" for open orders, \"history\" for filled/cancelled"
}
},
"additionalProperties": false
}No endpoints wrapped at confidence ≥ 0.70.
Parent server
SAP MCP Server
https://github.com/OOBE-PROTOCOL/sap-mcp
2/7 registries