Skip to main content
Glama

smart_money_flow

Are PROVEN smart-money / alpha wallets net-BUYING or net-SELLING this token RIGHT NOW? Backed by our proprietary cross-coin reputation universe — NOT a public whale-tracker or a wrapper around on-chain data you already have. Returns signal = SMART_CONVERGENCE (multiple proven wallets accumulating — early-demand) / SMART_DISTRIBUTION (proven wallets exiting — smart-money dumping) / SMART_SINGLE / null, with n_buyers, n_sellers. Call before entering to see if informed capital is actually behind a move. Solana (base58) or Robinhood-chain (0x). 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": {
      "token": "<token>"
    },
    "name": "smart_money_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes0x-address or base58 mint

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 most of it: it discloses the return signal vocabulary with interpretations, the companion fields n_buyers/n_sellers, supported chains, and a concrete cost/rate-limit model (free 10/day, then $0.01/call). It omits latency, caching/staleness of the 'RIGHT NOW' snapshot, and what a null result implies about data coverage.

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?

The core question and the return vocabulary are front-loaded, which is good. But promotional phrasing ('proprietary cross-coin reputation universe', 'smart-money dumping', heavy ALL-CAPS emphasis) and the pricing sentence consume space that could have carried behavioral detail.

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

Completeness4/5

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

For a one-parameter query tool with no output schema, the description covers what it returns (signal enum plus buyer/seller counts), when to call it, and its cost model — enough for correct invocation. The main remaining gap is that 'null' is listed without explaining whether it means no data, insufficient history, or genuinely no smart-money activity.

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?

Schema coverage is 100% and the single parameter is already documented, so the baseline is 3. The description adds value by naming the chains behind each address format ('Solana (base58) or Robinhood-chain (0x)'), which the schema only implies via '0x-address or base58 mint'.

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?

The description names a specific verb and resource ('are proven smart-money / alpha wallets net-BUYING or net-SELLING this token') and enumerates the exact output classification (SMART_CONVERGENCE / SMART_DISTRIBUTION / SMART_SINGLE / null). It also pre-empts confusion with a category of alternatives ('NOT a public whale-tracker or a wrapper around on-chain data you already have'), so an agent can distinguish it from generic on-chain tools without opening a 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?

It gives an explicit trigger: 'Call before entering to see if informed capital is actually behind a move,' which tells the agent when in a workflow this belongs. It does not name any specific sibling (e.g. informed_convergence, flow_inflection) 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