Skip to main content
Glama

informed_convergence

Are MULTIPLE independent proven-informed wallets CONVERGING on this Solana token right now? Our validated edge: a single informed wallet is noise, but a CLUSTER of independent informed wallets buying the same coin within a short window out-of-sample precedes up-moves. Returns confirmed (bool), n_informed (how many proven-informed wallets bought it in the last 6h), avg_informedness. Proprietary — built from our cross-coin informedness universe. Solana (base58). 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": "informed_convergence"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesSolana base58 mint

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 6h measurement window, the exact return fields (confirmed bool, n_informed, avg_informedness), the data provenance (proprietary cross-coin informedness universe), the chain/encoding, and the cost model (free 10/day, then $0.01/call). It omits latency, whether results are cached, and what happens when fewer than two wallets qualify, which keeps it from a 5.

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?

The core question is front-loaded, followed by the rationale, return shape, and pricing in a logical order. A few phrases ('Our validated edge', 'Proprietary — built from our cross-coin informedness universe') lean promotional, but they do convey data provenance, so little is pure waste.

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 read tool with no output schema, the description supplies the return fields, the time window, chain constraints, and quota/cost — enough for an agent to call it and interpret the result. Missing only edge-case behavior (no qualifying cluster, stale data) and any explicit alternative routing.

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 coverage is 100% for the single required 'token' parameter, and the description only restates 'Solana (base58)' — matching, not extending, the schema's 'Solana base58 mint'. Baseline 3 is appropriate when the schema does the work; no added meaning such as accepted formats or example mints is provided.

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

Purpose4/5

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

The description names a specific signal: whether multiple independent proven-informed wallets are buying the same Solana token within a short window, returning a boolean plus counts. That is a concrete verb+resource, and the 'single wallet is noise vs. cluster' framing implicitly separates it from single-wallet or aggregate-flow tools. It does not explicitly name a sibling alternative, so it stops short of a 5.

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

Usage Guidelines3/5

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

The phrase 'right now' and the 'last 6h' window give an implied usage context for a pre-entry convergence check, but the description never states when to prefer this over smart_money_flow, copy_signals, or timing_signal, nor any when-not condition. Usage is inferable rather than instructed.

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