Skip to main content
Glama
OOBE-PROTOCOL

SAP MCP Server

Meteora Create D L M M Pool

meteora_createDLMMPool

Create a Meteora DLMM pool by specifying token mints, bin step, initial price, and optional parameters like fee BPS, amounts, activation type and point.

Instructions

Create a Meteora DLMM (Discrete Liquidity Market Maker) pool. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintXYesToken X mint
mintYYesToken Y mint
feeBpsNoFee Bps parameter for Meteora Create D L M M Pool.
amountXNoRaw token amount (smallest unit)
amountYNoRaw token amount (smallest unit)
binStepYesBin step size (defines fee tier and price granularity)
creatorYesSolana public key (base58)
initialPriceYesInitial Price parameter for Meteora Create D L M M Pool.
activationTypeNoActivation Type parameter for Meteora Create D L M M Pool.
activationPointNoActivation Point parameter for Meteora Create D L M M Pool.
priceRoundingUpNoPrice Rounding Up parameter for Meteora Create D L M M Pool.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesMCP content blocks returned to the caller.
isErrorNoTrue when the tool result represents an application-level error.
Behavior2/5

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

Annotations show readOnlyHint=false and openWorldHint=true, but description adds no behavioral details beyond 'Create'. No mention of permissions, side effects, or on-chain complexity.

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

Conciseness5/5

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

Two sentences: first states core purpose, second provides SAP context. No wasted words, front-loaded.

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?

Despite high parameter count (11) and no explanation of DLMM or prerequisites, the description is too minimal. Output schema existence doesn't compensate for missing usage context.

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 provides 100% parameter coverage with descriptions. Description adds no extra meaning beyond schema fields.

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?

Description clearly states 'Create a Meteora DLMM pool' using specific verb and resource. Distinguishes from sibling tools like meteora_createDynamicPool and meteora_addDLMMLiquidity.

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?

Provides SAP MCP context and explicitly names alternative tools (sap_agent_identity_plan, etc.) for on-chain registration. Does not compare directly to other pool creation methods but gives relevant guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OOBE-PROTOCOL/sap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server