Skip to main content
Glama

My MCP Server

whale-wallet-tracker

Live Solana Mainnet whale-wallet-tracker ($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": "whale-wallet-tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a genuine behavioral trait beyond structure: a cost of $0.10 USDC charged via an x402 v2 PAYMENT-SIGNATURE header, which matters for an agent deciding whether to invoke it. However, it says nothing about whether the tool is read-only, whether it streams or returns a snapshot, rate limits, or failure behavior.

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 clause with no waste in a literal sense, but the brevity is under-specification rather than discipline. Half the text is a name echo and the rest is a payment note, so the token budget is misallocated.

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?

Two undocumented parameters, no output schema, and no annotations leave the agent with almost nothing. For a tool whose behaviour (live tracking of specific wallets and mints) is inherently ambiguous, the description is far too thin to call it correctly.

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 coverage is 0% and both parameters (mint, targetWallet) have no descriptions. The description does not mention either parameter, so the agent has no idea whether targetWallet is required for tracking, or what mint scopes the results to — likely a token filter versus a wallet filter. Complete compensation failure at low coverage.

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 ("whale-wallet-tracker") with a network qualifier ("Live Solana Mainnet"). It never states what the tool actually returns or what a "track" operation consists of — a live feed, a snapshot, a list of wallets? An agent cannot distinguish its output from siblings like smart-money-copy-scanner or holder-concentration-analyzer based on this text.

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 conditions, and no named alternative. The only extra information is a pricing note, which tells the agent nothing about when this tool is the right choice over the many sibling trackers and scanners.

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