Skip to main content
Glama

wallet_reputation

Informedness / alpha reputation of a Solana wallet, scored OUT-OF-SAMPLE: does this wallet's BUY tend to PRECEDE price-up moves? Proprietary metric from our tracked universe (1000+ wallets, cross-coin). Returns informedness_med / informedness_mean (how much its buys lead price, %), n (sample size), rel_score. Use it to weight copy-trading, rank a signal source, or screen a counterparty's informedness. Higher = more informed / price-leading; negative = its buys tend to precede DROPS. Free 10/day, then $0.01/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": {
      "wallet": "<wallet>"
    },
    "name": "wallet_reputation"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesSolana wallet address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the sign convention (negative means buys precede drops), the sample-size field n for reliability judgment, the source universe (1000+ tracked wallets, cross-coin), and the pricing/quota model (free 10/day then $0.01/call). What it omits is behavior for wallets outside the tracked universe and expected latency, which matters for a metered call.

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

Conciseness4/5

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

Front-loads the core question the metric answers, then the return fields, then use cases, then pricing — a sensible ordering for an agent scanning quickly. It is dense with useful content rather than padded, though the capitalized emphasis and compound clauses make it slightly harder to parse than necessary.

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 and no annotations, so the description must explain return values and cost, and it does both (informedness_med/informedness_mean, n, rel_score, plus the quota). For a one-parameter scoring endpoint, nothing an agent needs in order to decide and call is missing.

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

Parameters4/5

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

The single parameter is fully documented in the schema (base58 Solana address), so the schema does the syntax work. The description adds meaning the schema lacks: that scoring derives from a bounded tracked universe of 1000+ wallets, implying an arbitrary address may fall outside coverage — a nuance that affects whether the call is worth spending.

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-like operation on a specific resource: scoring a Solana wallet's informedness, defined as whether its buys precede price-up moves. It distinguishes itself from vague siblings by naming the exact metric family (out-of-sample informedness, not raw PnL or flow), so an agent can tell it apart from track_record or smart_money_flow without opening another schema.

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 three concrete applications — weighting copy-trading, ranking a signal source, screening a counterparty — which covers most realistic invocation contexts. It does not name a specific alternative sibling or state when NOT to use it, 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