SAP MCP Server

Raydium-pools Create C L M M

raydium-pools_createCLMM

Create a Raydium CLMM (Concentrated Liquidity) pool with a price range. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.

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: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

Input Schema

TableJSON Schema

Name	Required	Description
`mintA`	Yes	Token mint address (base58)
`mintB`	Yes	Token mint address (base58)
`amountA`	Yes	Initial liquidity for token A
`amountB`	Yes	Initial liquidity for token B
`creator`	Yes	Solana public key (base58)
`startTime`	No	Start Time parameter for Raydium-pools Create C L M M.
`priceLower`	Yes	Lower price bound for liquidity range
`priceUpper`	Yes	Upper price bound for liquidity range
`tickSpacing`	Yes	Tick spacing (defines fee tier: 1=0.01%, 10=0.05%, 60=0.3%, 200=1%)
`initialPrice`	Yes	Initial price of token A in terms of token B

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 changedJul 24, 2026

addedInput schema / description

Added value: +"Raydium-pools Create C L M M 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: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial. Use exact field names from this schema; do not guess aliases or include private key material."

First observedJul 13, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already indicate non-readonly, open-world, non-idempotent, non-destructive. The description adds SAP routing context but does not disclose behavioral traits like side effects, costs, or preconditions beyond what annotations imply. The creation action is clear but not elaborated.

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 description is unnecessarily verbose with boilerplate SAP MCP text repeated from the schema. The first sentence is concise, but the rest could be omitted or condensed. The structure front-loads the purpose but then adds redundant information.

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?

Given the existence of sibling tools for creating other pool types, the description fails to explain when to choose CLMM. It lacks domain-specific context like prerequisites (token ownership, price range constraints) and use cases. The output schema covers return values, but operational context is missing.

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 10 parameters have descriptions in the input schema. The tool description does not add any additional meaning or context beyond the schema, so baseline 3 is appropriate.

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 first sentence clearly states the tool creates a Raydium CLMM pool with a price range. However, it does not differentiate from sibling tools like raydium-pools_createAMMv4 and raydium-pools_createCPMM, which have similar purposes.

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

Usage Guidelines2/5

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

The description provides extensive generic SAP MCP execution guidance (pricing, routing, signing) but no guidance on when to use this specific tool versus its siblings. No context on prerequisites or use cases for creating a CLMM pool over other pool types.

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.