Skip to main content
Glama

My MCP Server

orca-whirlpool-scanner

Live Solana Mainnet orca-whirlpool-scanner ($0.10 USDC via x402 v2 PAYMENT-SIGNATURE header)

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": "orca-whirlpool-scanner"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/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 does disclose one genuinely useful trait: the tool is a paid endpoint ($0.10 USDC, x402 v2 PAYMENT-SIGNATURE header), which implies an auth/payment requirement. However, it says nothing about whether the operation is read-only, what data is returned, latency, or rate limits for a tool whose name suggests active scanning.

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

Conciseness3/5

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

It is a single short sentence with zero padding, and the payment requirement is placed up front. But the brevity comes at the cost of substance rather than from efficient wording, so it does not earn a high score.

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 a scanner with two free-form, undocumented parameters and no output schema, the definition should explain what is scanned and what is returned. Only the payment mechanism is covered, leaving the core contract of the tool unspecified.

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?

Schema description coverage is 0% for both parameters, and the description never mentions mint or targetWallet. An agent must guess whether mint is required for a pool lookup, whether targetWallet filters results, or whether omitting both yields a global scan (required list is empty). This is a complete gap in parameter meaning.

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 essentially restates the tool name, adding only "Live" and "Solana Mainnet" as scope qualifiers. There is no verb describing what the scanner actually does or returns, so an agent cannot tell whether it detects new pools, prices, or arbitrage opportunities, nor how it differs from siblings like liquidity-pool-sniffer.

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?

No when-to-use guidance, no preconditions, and no alternatives are named. The only actionable information is the price and payment mechanism, which does not help an agent decide when this tool is the right choice over the many other Solana scanners in the catalog.

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