Skip to main content
Glama

meteora-dlmm-yield-finder

meteora-dlmm-yield-finder on Solana Mainnet; swap plans are unsigned

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "meteora-dlmm-yield-finder"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
amountNoInput amount in atomic units
tipPayerNo
inputMintNo
outputMintNo
slippageBpsNo
tipLamportsNo
takingAmountNoLimit order output amount in atomic units
targetWalletNo
transactionsNoUnsigned base64 transactions for a Jito bundle plan
userPublicKeyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / amount
      Added value: +{
      +  "description": "Input amount in atomic units",
      +  "type": "string"
      +}
    • addedInput schema / properties / inputMint
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / outputMint
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / slippageBps
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / takingAmount
      Added value: +{
      +  "description": "Limit order output amount in atomic units",
      +  "type": "string"
      +}
    • addedInput schema / properties / tipLamports
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / tipPayer
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / transactions
      Added value: +{
      +  "description": "Unsigned base64 transactions for a Jito bundle plan",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / userPublicKey
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

D1.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Swap plans are unsigned' is a genuinely useful disclosure (the tool does not broadcast; the caller must sign), but nothing is said about permissions, side effects, what wallet is used, or what the response contains.

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?

Two short clauses with no filler, but the brevity is under-specification rather than conciseness. The one substantive fact (unsigned plans) is buried after a redundant restatement of the tool name.

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?

For an 11-parameter, zero-annotation, no-output-schema transaction-planning tool, the definition is far too thin. An agent cannot tell what it returns (base64 transactions?), which parameters are required, or how to choose between the swap, limit-order, and Jito-bundle paths implied by the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Eleven parameters with only 27% schema coverage, and the description explains none of them. Fields like tipPayer, tipLamports, targetWallet, transactions, and the mint/inputMint/outputMint trio have no meaning added anywhere, and it is unclear whether the tool is swap-plan oriented or limit-order oriented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name and adds only 'on Solana Mainnet', so the actual operation is never stated with a verb. Worse, the name says 'yield finder' while the schema fields (slippageBps, takingAmount, transactions for a Jito bundle) describe swap/limit-order planning, leaving the real purpose ambiguous.

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?

There is no when-to-use guidance at all, and no reference to alternatives such as jito-bundle-dispatcher, raydium-swap-automator, or limit-order-sniper. 'on Solana Mainnet' is a scope note, not usage guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources