SAP MCP Server

sap steve launch build dbc

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: hosted unsigned transaction builder. 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.

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 steve launch build dbc.",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    {
+      "description": "Migration Quote Threshold parameter for sap steve launch build dbc.",
+      "pattern": "^\\d+(?:\\.\\d*)?$",
+      "type": "string"
+    }
+  ]
+}

AddedSep 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), and the description adds real context beyond them: it is a hosted unsigned-transaction builder, never receives keypair bytes, is a paid call requiring cost estimation and x402 routing, and the returned value must be signed locally. It does not state what happens on partial failure of the multi-step build or rate/limit behavior.

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 launch lifecycle is front-loaded and efficient in two sentences, but the second paragraph is a generic SAP execution-guidance block that is duplicated verbatim inside the input schema description, adding redundancy without new tool-specific information.

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

Completeness5/5

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

With an output schema present, 100% parameter coverage, and full annotations, the description supplies everything else the agent needs: the transaction lifecycle, the payment/estimation flow, the signer boundary, the blockhash freshness requirement, and the follow-up dev-buy call.

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% with all 17 parameters documented, so the schema already carries parameter meaning. The description only adds the quote-token support surface (SOL, USDC, validated SPL/Token-2022), which the schema also states, so it does not meaningfully exceed the baseline.

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?

States a specific verb and resource ('Build a Steve-native direct Meteora DBC launch') and enumerates the exact sub-steps (create config, initialize pool, transfer creator authority to the 70/30 escrow PDA, initialize escrow). It also distinguishes the tool from its closest sibling by stating that the initial buy is a separate call to sap_steve_launch_build_dbc_dev_buy.

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?

Gives explicit sequencing: estimate cost first, pay/build, then finalize locally, and the dev buy must happen after pool confirmation with a fresh blockhash. It does not, however, differentiate against the many other launch siblings in the list (sap_perpspad_launch_dbc, sap_meteora_build_launchpad_migration), so an agent has no rule for choosing among them.

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.