SAP MCP Server

sap perpspad launch dbc

sap_perpspad_launch_dbc

DEPRECATED alias; use sap_steve_launch_build_dbc. Build a Steve-native direct Meteora DBC launch: create config, initialize pool, transfer creator authority to the 70/30 escrow PDA, then initialize escrow. A requested initial buy is built separately after pool confirmation with sap_steve_launch_build_dbc_dev_buy and a fresh blockhash. Supports SOL, USDC, and validated SPL/Token-2022 quote mints.

SAP MCP execution guidance: 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.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Coin display name
`payer`	Yes	Transaction payer + initial pool creator (signs the returned transactions client-side)
`quote`	No	Quote token: SOL, USDC, or CUSTOM with quoteMint. Custom SPL/Token-2022 mints are validated on-chain.
`ticker`	Yes	Coin ticker, A-Z 0-9 only (e.g. MOON)
`leverage`	No	Perp backing: integer leverage 1-10. REQUIRED together with underlying and direction (all-or-nothing).
`devBuySol`	No	Deprecated alias for devBuyAmount (SOL launches only)
`direction`	No	Perp backing: long\|short. REQUIRED together with underlying and leverage (all-or-nothing).
`quoteMint`	No	Required when quote=CUSTOM: SPL or Token-2022 mint with 6-9 decimals and no unsupported transfer behavior.
`underlying`	No	Perp backing: Phoenix market symbol (e.g. SOL, TSLA, OIL). A-Z 0-9, 1-12 chars. REQUIRED together with leverage and direction (all-or-nothing).
`agentWallet`	Yes	Agent wallet: receives 70% of claimed trading fees; also the leftover-token receiver
`metadataUri`	No	Exact permanent HTTPS URI of the Metaplex JSON (for example an IPFS/Arweave gateway URL). Preferred for production launches.
`solPriceUsd`	No	Live SOL/USD reference. Required for non-SOL quotes.
`devBuyAmount`	No	Initial buy amount, denominated in the selected quote token
`quotePriceUsd`	No	Live USD price of one quote token. Required for non-SOL quotes.
`latestBlockhash`	Yes	FRESH mainnet blockhash fetched by the CALLER (getLatestBlockhash) — guarantees signability from the client. Required.
`metadataBaseUrl`	No	HTTPS base URL used to build the Metaplex JSON URI
`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 launch dbc.",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    {
+      "description": "Migration Quote Threshold parameter for sap perpspad launch dbc.",
+      "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 19, 2026

addedInput schema / properties / metadataUri

Added value: +{
+  "description": "Exact permanent HTTPS URI of the Metaplex JSON (for example an IPFS/Arweave gateway URL). Preferred for production launches.",
+  "type": "string"
+}

Changed3 schema fields changedSep 17, 2026

changedInput schema / properties / payer / description

Previous value: -"Transaction payer + pool creator (signs all three txs client-side)"New value: +"Transaction payer + initial pool creator (signs the returned transactions client-side)"

changedInput schema / properties / quote / description

Previous value: -"Optional quote token hint (e.g. SOL, USDC). USDC is NOT yet supported by the direct DBC builder and fails fast."New value: +"Quote token: SOL, USDC, or CUSTOM with quoteMint. Custom SPL/Token-2022 mints are validated on-chain."

addedInput schema / properties / quoteMint

Added value: +{
+  "description": "Required when quote=CUSTOM: SPL or Token-2022 mint with 6-9 decimals and no unsupported transfer behavior.",
+  "type": "string"
+}

Changed5 schema fields changedSep 17, 2026

addedInput schema / properties / devBuyAmount

Added value: +{
+  "description": "Initial buy amount, denominated in the selected quote token",
+  "type": "number"
+}

changedInput schema / properties / devBuySol / description

Previous value: -"Dev-buy in SOL (0.1-5), spent via swap after pool init"New value: +"Deprecated alias for devBuyAmount (SOL launches only)"

removedInput schema / properties / imageUrl

Removed value: -{
-  "description": "Optional coin image URL (embedded in the metadata uri)",
-  "type": "string"
-}

addedInput schema / properties / metadataBaseUrl

Added value: +{
+  "description": "HTTPS base URL used to build the Metaplex JSON URI",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "ticker",
-  "name",
-  "agentWallet",
-  "payer",
-  "devBuySol",
-  "latestBlockhash"
-]New value: +[
+  "ticker",
+  "name",
+  "agentWallet",
+  "payer",
+  "latestBlockhash"
+]

Changed4 schema fields changedSep 16, 2026

addedInput schema / properties / direction

Added value: +{
+  "description": "Perp backing: long|short. REQUIRED together with underlying and leverage (all-or-nothing).",
+  "enum": [
+    "long",
+    "short"
+  ],
+  "type": "string"
+}

addedInput schema / properties / leverage

Added value: +{
+  "description": "Perp backing: integer leverage 1-10. REQUIRED together with underlying and direction (all-or-nothing).",
+  "type": "number"
+}

addedInput schema / properties / quote

Added value: +{
+  "description": "Optional quote token hint (e.g. SOL, USDC). USDC is NOT yet supported by the direct DBC builder and fails fast.",
+  "type": "string"
+}

addedInput schema / properties / underlying

Added value: +{
+  "description": "Perp backing: Phoenix market symbol (e.g. SOL, TSLA, OIL). A-Z 0-9, 1-12 chars. REQUIRED together with leverage and direction (all-or-nothing).",
+  "type": "string"
+}

Changed2 schema fields changedSep 16, 2026

addedInput schema / properties / latestBlockhash

Added value: +{
+  "description": "FRESH mainnet blockhash fetched by the CALLER (getLatestBlockhash) — guarantees signability from the client. Required.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "ticker",
-  "name",
-  "agentWallet",
-  "payer",
-  "devBuySol"
-]New value: +[
+  "ticker",
+  "name",
+  "agentWallet",
+  "payer",
+  "devBuySol",
+  "latestBlockhash"
+]

AddedSep 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the mutation profile is covered structurally. The description adds real behavioral detail beyond that: the multi-step transaction sequence, that creator authority is transferred to a 70/30 escrow PDA, and the signer boundary (hosted builders never receive keypair bytes, value-moving results finalize locally). It stops short of describing failure modes or what happens to an in-flight sequence if a step fails, so it is a strong 4 rather than a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The functional content is well front-loaded: deprecation warning, then the step sequence, then the dev-buy handoff. However, a large trailing block of generic SAP MCP boilerplate (intent/pricing/routing/signer boundary) is duplicated almost verbatim in the input schema description, so several sentences do not earn their place in this field.

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?

For a 17-parameter, high-complexity builder with an output schema and full annotation coverage, the definition supplies the key missing context: deprecation, replacement tool, the build sequence, and the local-signing boundary. Return values need not be explained because an output schema exists. It is complete enough to call correctly, with only minor gaps around sequence-failure handling.

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 all 17 parameters are documented in the schema itself, which sets the baseline at 3. The description only adds quote-token breadth (SOL, USDC, validated SPL/Token-2022), which the schema's quote/quoteMint fields already convey. No additional syntax or constraint meaning is contributed.

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 names the exact operation (build a Steve-native direct Meteora DBC launch) and then decomposes it into concrete steps: create config, initialize pool, transfer creator authority to the 70/30 escrow PDA, initialize escrow. It also immediately flags itself as a deprecated alias for sap_steve_launch_build_dbc, so the agent can distinguish it from that sibling without reading either schema.

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?

Explicit when-not ('DEPRECATED alias; use sap_steve_launch_build_dbc') and explicit follow-up routing ('a requested initial buy is built separately after pool confirmation with sap_steve_launch_build_dbc_dev_buy and a fresh blockhash'). Both the replacement and the sequencing constraint are stated, leaving nothing to inference.

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.