SAP MCP Server

sap perpspad dbc config preview

sap_perpspad_dbc_config_preview

DEPRECATED alias; use sap_steve_launch_preview_dbc. PRE-LAUNCH DBC economics readout: decodes the exact Meteora DBC config the gateway will sign (scaled per quote decimals) and simulates the dev-buy with the official SDK swap math. Returns migration threshold, start price, curve breakdown, tokens out (supply-capped) and min-out after slippage. Call this instead of estimating locally — the frontend renders these values verbatim.

SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. 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
`quoteMint`	Yes	Quote mint address (SOL = wrapped SOL mint, CUSTOM = the verified mint)
`slippageBps`	No	Dev-buy slippage in bps (default 300)
`solPriceUsd`	No	Live SOL/USD reference; required for non-SOL quotes.
`devBuyAmount`	No	Human dev-buy amount in quote units (e.g. 1 SOL, 1000 OOBE). 0/omitted = curve facts only.
`quotePriceUsd`	No	Live USD price of one quote token; required for non-SOL quotes.
`migrationQuoteThreshold`	No	Optional positive quote reserve target that graduates the bonding curve to DAMM v2, in human quote-token units. Decimal strings preserve exact large custom-quote amounts.

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 changedSep 27, 2026

addedInput schema / properties / migrationQuoteThreshold

Added value: +{
+  "description": "Optional positive quote reserve target that graduates the bonding curve to DAMM v2, in human quote-token units. Decimal strings preserve exact large custom-quote amounts.",
+  "oneOf": [
+    {
+      "description": "Migration Quote Threshold parameter for sap perpspad dbc config preview.",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    {
+      "description": "Migration Quote Threshold parameter for sap perpspad dbc config preview.",
+      "pattern": "^\\d+(?:\\.\\d*)?$",
+      "type": "string"
+    }
+  ]
+}

Changed2 schema fields changedSep 22, 2026

addedInput schema / properties / quotePriceUsd

Added value: +{
+  "description": "Live USD price of one quote token; required for non-SOL quotes.",
+  "type": "number"
+}

addedInput schema / properties / solPriceUsd

Added value: +{
+  "description": "Live SOL/USD reference; required for non-SOL quotes.",
+  "type": "number"
+}

Changed1 schema field changedSep 21, 2026

changedInput schema / description

Previous value: -"sap perpspad dbc config preview input schema. Intent: SAP MCP tool 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."New value: +"sap perpspad dbc config preview input schema. Intent: SAP MCP tool workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. 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."

AddedSep 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=true, and the description adds useful non-schema context: free, no x402 payment, hosted reads/builders never receive keypair bytes, and the frontend renders returned values verbatim (i.e., don't recompute). It does not explain what the non-readOnlyHint=false implies for a tool that is described as a readout/simulation, leaving a small gap.

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 deprecation notice is front-loaded, followed by purpose, return values, and routing guidance in a predictable order. The appended 'SAP MCP execution guidance' block is partly generic boilerplate (pricing/routing/signer boundary) that is repeated verbatim in the schema description, so it costs some efficiency.

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?

With an output schema present, the description needn't enumerate return values, yet it does so briefly and consistently. It covers deprecation, cost model, and the signer boundary, which is enough for an agent to call a 6-param preview tool correctly, though it never clarifies the tension between being deprecated and being recommended.

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 description coverage is 100%, so the baseline is 3; params already document defaults (slippageBps default 300), the solPriceUsd/quotePriceUsd prerequisite for non-SOL quotes, and devBuyAmount units. The description adds only indirect hints (values scaled per quote decimals, supply-capped tokens out, min-out after slippage) that mostly describe outputs rather than parameter meaning.

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 states a specific verb+resource: it decodes the exact Meteora DBC config the gateway will sign and simulates the dev-buy, listing concrete outputs (migration threshold, start price, curve breakdown, tokens out, min-out). It also names the successor tool, but the 'DEPRECATED alias' framing followed by 'Call this instead of estimating locally' leaves mild ambiguity about whether this tool or its successor is the intended target.

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?

It explicitly names the alternative (sap_steve_launch_preview_dbc) and the condition for preferring it via deprecation, and adds 'Call this instead of estimating locally' plus the requirement of a live SOL/USD reference for non-SOL quotes. However, the deprecation redirect and the retention of 'call this' guidance pull in opposite directions, so the agent must infer which one to actually invoke.

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.