Skip to main content
Glama

liquidity-pool-sniffer

liquidity-pool-sniffer 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": "liquidity-pool-sniffer"
  }
}

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.6/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. It usefully discloses that swap plans are unsigned and that it operates on Solana Mainnet, but says nothing about whether it reads state, builds transactions, requires auth, submits bundles, or has side effects.

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 short but severely under-specified rather than efficiently concise. It lacks a front-loaded purpose statement and splits attention between a name restatement and a partial safety note.

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

Completeness1/5

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

For an 11-parameter tool with no annotations and no output schema, this definition is far too thin. An agent cannot determine what the tool returns, which parameters are needed, or how it relates to the many sibling tools.

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?

With 11 parameters and only 27% schema description coverage, the description must compensate for many undocumented fields such as mint, inputMint, outputMint, slippageBps, tipPayer, targetWallet, and userPublicKey. It adds no meaning for any parameter.

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 mostly restates the tool name ('liquidity-pool-sniffer') and adds only chain context ('Solana Mainnet'). It never states a specific action or output, so an agent cannot confidently distinguish it from siblings like orca-whirlpool-scanner or raydium-swap-automator.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no exclusions, and no named alternative. 'Swap plans are unsigned' is a behavioral note, not a usage condition.

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