SAP MCP Server

Jupiter Swap Instructions

jupiter_swapInstructions

Destructive

Generate individual swap instructions for composition with other Solana transactions. Supports fee account, token ledger, and compute unit parameters.

Instructions

Get individual swap instructions instead of a full transaction. Useful for composing with other instructions. 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.

Input Schema

TableJSON Schema

Name	Required	Description
`feeAccount`	No	Solana wallet public key (base58)
`quoteResponse`	Yes	The full quoteResponse object from getQuote
`userPublicKey`	Yes	Solana wallet public key (base58)
`useTokenLedger`	No	Use Token Ledger mint, symbol, or token identifier used by Jupiter Swap Instructions.
`wrapAndUnwrapSol`	No	Wrap And Unwrap Sol parameter for Jupiter Swap Instructions.
`useSharedAccounts`	No	Use Shared Accounts parameter for Jupiter Swap Instructions.
`asLegacyTransaction`	No	As Legacy Transaction transaction payload used by Jupiter Swap Instructions.
`destinationTokenAccount`	No	Solana wallet public key (base58)
`dynamicComputeUnitLimit`	No	Dynamic Compute Unit Limit controlling the maximum number of results returned by Jupiter Swap Instructions.
`computeUnitPriceMicroLamports`	No	Compute Unit Price Micro Lamports value to use for Jupiter Swap Instructions.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`content`	Yes	MCP content blocks returned to the caller.
`isError`	No	True when the tool result represents an application-level error.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.7.4Jul 14, 2026

addedInput schema / properties / asLegacyTransaction / description

Added value: +"As Legacy Transaction transaction payload used by Jupiter Swap Instructions."

addedInput schema / properties / computeUnitPriceMicroLamports / description

Added value: +"Compute Unit Price Micro Lamports value to use for Jupiter Swap Instructions."

addedInput schema / properties / dynamicComputeUnitLimit / description

Added value: +"Dynamic Compute Unit Limit controlling the maximum number of results returned by Jupiter Swap Instructions."

addedInput schema / properties / useSharedAccounts / description

Added value: +"Use Shared Accounts parameter for Jupiter Swap Instructions."

addedInput schema / properties / useTokenLedger / description

Added value: +"Use Token Ledger mint, symbol, or token identifier used by Jupiter Swap Instructions."

addedInput schema / properties / wrapAndUnwrapSol / description

Added value: +"Wrap And Unwrap Sol parameter for Jupiter Swap Instructions."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "content": {
+      "description": "MCP content blocks returned to the caller.",
+      "items": {
+        "properties": {
+          "text": {
+            "description": "Human-readable JSON or text returned by the tool.",
+            "type": "string"
+          },
+          "type": {
+            "description": "MCP content block type, usually text.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "type"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "isError": {
+      "description": "True when the tool result represents an application-level error.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "content"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jun 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description does not contradict annotations. It adds context about composing and SAP integration. While it doesn't elaborate on side effects, the destructiveHint is implied by 'swap instructions'. No annotation contradiction.

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?

Two concise sentences, front-loaded with purpose. No wasted words.

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?

The description mentions composition and SAP MCP workflow. While it doesn't explicitly state the dependency on jupiter_getQuote, the schema's parameter description for quoteResponse covers that. Given the output schema exists and parameters are well-documented, it is sufficiently complete.

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

Parameters3/5

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

Schema coverage is 100%, so all parameters are described in the schema. The tool description adds no additional parameter meaning beyond what's in the schema, meeting the baseline expectation.

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 verb 'Get' and the resource 'individual swap instructions', distinguishing it from a full transaction. It also implicitly separates from siblings like jupiter_swap by focusing on instruction composition.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Useful for composing with other instructions' and provides SAP MCP context with guidance on when to use this tool versus SAP transaction tools for signing. This gives clear decision support.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server