Skip to main content
Glama

My MCP Server

smart-money-copy-scanner

Live Solana Mainnet smart-money-copy-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": "smart-money-copy-scanner"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does usefully disclose that this is a live mainnet tool requiring an x402 v2 PAYMENT-SIGNATURE header and costing $0.10 USDC, which is real operational context. However, it says nothing about whether the call is read-only, what the response contains, latency, or failure modes when payment is missing — gaps that matter a lot for an unannotated tool.

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 compact clause with no filler, and the pricing/payment detail is front-loaded rather than buried. The problem is under-specification rather than verbosity — the space saved is space that should have gone to describing the operation.

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 paid, unannotated scanner with two undocumented optional parameters and no output schema, the description is materially incomplete. It covers cost and payment mechanics but leaves an agent unable to determine what the tool produces or how to shape a call.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, so the description must compensate and does not: 'mint' and 'targetWallet' are never mentioned or explained. An agent cannot tell whether supplying targetWallet narrows the scan or is an alternative mode, nor what happens when both are omitted (0 required parameters).

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 largely restates the tool name ('smart-money-copy-scanner') and adds only environment and pricing metadata ('Live Solana Mainnet', '$0.10 USDC'). It never states the actual action — what is scanned, what constitutes 'smart money', or what a caller receives — so it is closer to a tautology than a specific verb+resource statement.

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, no exclusions, and no pointer to alternatives among closely related siblings such as whale-wallet-tracker or mempool-alpha-scanner. The only conditional information is the payment requirement, which is about cost, not selection.

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