Skip to main content
Glama

Smart money score

smart_money
Read-only

Analyze any Solana wallet's trading intelligence. Scores wallets 0-100 as Smart Money based on swap history: win rate, profit factor, early-entry ability, consistency, and diversification. Returns per-token trade stats, realized PnL in SOL, best/worst trades, and a human-readable label (Smart Money / Above Average / Average / Below Average). Use to evaluate copy-trade targets, track whale wallets, or assess counterparty skill. Costs $0.05 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "walletAddress": "<walletAddress>"
    },
    "name": "smart_money"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletAddressYesSolana wallet address (base58) to analyze

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing a per-call cost of $0.05 USDC, the scoring methodology, and the exact payload contents (per-token stats, realized PnL in SOL, best/worst trades, text label). Cost disclosure is exactly the kind of behavior an agent needs before deciding to invoke a paid tool.

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

Conciseness5/5

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

Four tightly packed sentences with zero filler: purpose and methodology first, then return shape, then use cases, then cost. Front-loading is correct and every sentence carries distinct information.

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

Completeness5/5

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

There is no output schema, but the description fully compensates by enumerating the returned fields and the label vocabulary (Smart Money / Above Average / Average / Below Average). Combined with the cost note and the single required parameter, an agent has everything needed to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100% and the single walletAddress parameter is already documented as a base58 Solana address. The description adds nothing about format, validation, or behavior for that parameter, so it sits at the baseline rather than adding value.

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

Purpose5/5

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

States a specific verb and resource ('Analyze any Solana wallet's trading intelligence') and pins down the output precisely: a 0-100 Smart Money score derived from win rate, profit factor, early-entry ability, consistency, and diversification. This mechanically separates it from siblings like wallet_pnl, wallet_profile, and top_traders without needing to name them.

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

Usage Guidelines4/5

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

Gives concrete use cases ('evaluate copy-trade targets, track whale wallets, or assess counterparty skill'), which tells the agent when this tool is the right pick. It does not name a specific alternative or state exclusions against wallet_pnl / wallet_profile, so it stops short of full routing guidance.

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