Skip to main content
Glama
MadeOnSol

MadeOnSol — Solana memecoin intelligence

by MadeOnSol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

madeonsol_kol_coordination

Read-onlyIdempotent

Detect tokens with multiple KOL accumulations using a coordination score, peak activity window, and market cap context to identify early cluster formations.

Instructions

KOL convergence signals (v1.2) — tokens being accumulated by multiple KOLs. Response includes peak_kols/peak_buys (busiest window slice), exited_count (net-flow-negative wallets), 0-100 coordination_score, and (v1.2 / 2026-05-06) market_cap_usd_at_first_buy + market_cap_usd + last_price_usd so you can see whether the cluster formed at micro-cap or after the chart was already running. Blacklist filters WIF/BONK/stables by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNoTime period for coordination analysis24h
min_kolsNoMinimum number of KOLs converging on the same token
limitNoNumber of coordination signals to return
min_avg_winrateNoPRO+: require cluster avg winrate_7d >= N (0-100)
unique_strategiesNoPRO+: require >= N distinct strategies in cluster
include_majorsNov1.1: include major memecoins (WIF/BONK/POPCAT). Default false.
window_minutesNov1.1: peak-density window (1-60). Default 15.
min_scoreNov1.1: minimum composite coordination_score (0-100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.4

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint as true/true/true/false, so the safety profile is clear. The description adds behavioral context beyond annotations, such as the response fields (peak_kols, exited_count, coordination_score), blacklisting behavior, and version details.

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 description is moderately long but efficient, front-loading the main purpose and version, then detailing response fields and blacklisting. It is well-structured and avoids redundancy.

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?

Given no output schema, the description explains key response fields (peak_kols, exited_count, coordination_score, market_cap fields) adequately. It covers the blacklist default and version, but could be more exhaustive given the complexity of the tool.

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%, so each parameter already has a description. The main description does not add significant meaning to the parameters themselves, though it mentions response fields that depend on parameters like min_kols and min_score.

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 clearly states the tool provides 'KOL convergence signals (v1.2) — tokens being accumulated by multiple KOLs.' It lists specific response fields and distinguishes from other KOL tools by its focus on coordination signals.

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 description does not explicitly guide when to use this tool versus alternatives, nor does it state when not to use it. While the purpose is clear, no exclusionary or comparative guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools