Skip to main content
Glama

My MCP Server

validator-stake-tracker

Live Solana Mainnet validator-stake-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": "validator-stake-tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/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 disclose genuinely useful non-schema behavior: the tool is paid ($0.10 USDC) and requires an x402 v2 PAYMENT-SIGNATURE header. However, it omits read-only vs mutating nature, rate limits, latency/freshness guarantees for 'live' data, and error behavior on unpaid calls.

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?

A single short line with no filler, but the space spent on payment mechanics is not matched by any purpose detail. It is concise to the point of under-specification rather than being front-loaded with the information an agent needs.

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 two-parameter live data tool with no annotations, no output schema, and zero schema coverage, the description should explain what is returned and how the two parameters shape the query. Instead it covers only identity and pricing, leaving the core contract undocumented.

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 it does not. 'mint' and 'targetWallet' are left entirely unexplained — it is unclear whether mint identifies a validator vote account, a stake pool token, or an SPL token, and what targetWallet scopes.

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

Purpose3/5

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

The description restates the tool name ('validator-stake-tracker') and adds that it is live Solana Mainnet data, but never states a verb or what data is actually returned — stake amounts? validator list? per-wallet stakes? An agent cannot distinguish its function from siblings like whale-wallet-tracker or holder-concentration-analyzer from 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 prerequisites, and no mention of alternatives. The only contextual hint is 'Live Solana Mainnet,' which implies real-time use but says nothing about when this tool beats the other 23 tracker/scanner siblings.

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