SAP MCP Server

magicblock swap quote

magicblock_swap_quote

Destructive

Get a swap quote between two SPL mints (proxies Triton Metis swap API). Pass the result into magicblock_swap. Lightweight read tier; use this before any value-moving swap.

SAP MCP execution guidance: Intent: Solana value-action or trading workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

Input Schema

TableJSON Schema

Name	Required	Description
`amount`	Yes	Raw amount to swap (unsigned integer string, e.g. '1000000')
`swapMode`	No	Swap mode: fixed input or fixed output amount
`inputMint`	Yes	Input token mint address
`outputMint`	Yes	Output token mint address
`maxAccounts`	No	Approximate maximum account budget for the route (default 64)
`slippageBps`	No	Slippage threshold in basis points (e.g. 50 = 0.5%)
`platformFeeBps`	No	Optional platform fee in basis points
`onlyDirectRoutes`	No	Limit routing to a single hop (default false)
`restrictIntermediateTokens`	No	Restrict intermediate tokens to a more stable set (default false)

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.

Changed1 schema field changedAug 26, 2026

changedInput schema / description

Previous value: -"magicblock swap quote input schema. Intent: Solana value-action or trading workflow. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. Use exact field names from this schema; do not guess aliases or include private key material."New value: +"magicblock swap quote input schema. Intent: Solana value-action or trading workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. Use exact field names from this schema; do not guess aliases or include private key material."

AddedAug 18, 2026

TDQS

C2.8/5.0

Behavior1/5

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

The description says 'Lightweight read tier' and 'Get a swap quote,' which describes a read-only operation, but the annotations set readOnlyHint=false and destructiveHint=true. This is a direct contradiction. The SAP signer-boundary note adds useful context but cannot reconcile the conflicting 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.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are concise and front-load the core purpose, but the SAP MCP execution guidance block is long, repetitive boilerplate that duplicates text already present in the schema description. It dilutes the definition and weakens overall conciseness.

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

Completeness2/5

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

With full parameter coverage and an output schema, the main gaps are the contradictory annotation/description relationship and the lack of differentiation from magicblock_swapQuote. The SAP payment and signer-boundary context is present, but the conflicting read/write/destructive signals leave the agent without a coherent model of the tool's actual behavior.

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?

The input schema provides complete descriptions for all 9 parameters, so the baseline is 3. The description adds only 'between two SPL mints' and does not explain amount format, slippage, swapMode, or other parameters beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb and resource: 'Get a swap quote between two SPL mints' and distinguishes this from execution by saying 'Pass the result into magicblock_swap.' However, it does not differentiate from the near-identical sibling magicblock_swapQuote, leaving potential confusion about which quote tool to select.

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 gives explicit usage context: 'Lightweight read tier; use this before any value-moving swap' and names the downstream tool magicblock_swap. It does not mention alternative quote tools or explicitly say when not to use it, so the guidance is clear but not fully exhaustive.

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

All SAP MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.