Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_kol_hot_tokens

Read-onlyIdempotent

Identify tokens with increasing KOL buyer interest as early signals. Filter by buyer quality and strategy diversity with PRO+ options.

Instructions

KOL momentum tokens — tokens with accelerating KOL buy interest, early signals before coordination triggers. PRO+ adds buyer-quality filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNoTime period: 1h or 6h6h
min_kolsNoMinimum KOL buyers to include a token
limitNoNumber of hot tokens to return
min_avg_winrateNoPRO+: require avg winrate_7d of buyers >= N (0-100)
unique_strategiesNoPRO+: require >= N distinct strategies among buyers

Implementation Reference

  • The full tool definition including handler function for 'madeonsol_kol_hot_tokens'. It calls query('/api/x402/kol/tokens/hot') with period, min_kols, limit, and optional PRO+ filters min_avg_winrate and unique_strategies.
    server.tool(
      "madeonsol_kol_hot_tokens",
      "KOL momentum tokens — tokens with accelerating KOL buy interest, early signals before coordination triggers. PRO+ adds buyer-quality filters.",
      {
        period: z.enum(["1h", "6h"]).default("6h").describe("Time period: 1h or 6h"),
        min_kols: z.number().min(1).max(20).default(1).describe("Minimum KOL buyers to include a token"),
        limit: z.number().min(1).max(50).default(20).describe("Number of hot tokens to return"),
        min_avg_winrate: z.number().optional().describe("PRO+: require avg winrate_7d of buyers >= N (0-100)"),
        unique_strategies: z.number().optional().describe("PRO+: require >= N distinct strategies among buyers"),
      },
      readOnlyAnnotations,
      async ({ period, min_kols, limit, min_avg_winrate, unique_strategies }) => {
        const params: Record<string, string | number> = { period, min_kols, limit };
        if (min_avg_winrate !== undefined) params.min_avg_winrate = min_avg_winrate;
        if (unique_strategies !== undefined) params.unique_strategies = unique_strategies;
        return { content: [{ type: "text" as const, text: await query("/api/x402/kol/tokens/hot", params) }] };
      }
    );
  • Zod input schema for the tool: period (1h|6h), min_kols (1-20), limit (1-50), and optional PRO+ params min_avg_winrate and unique_strategies.
    {
      period: z.enum(["1h", "6h"]).default("6h").describe("Time period: 1h or 6h"),
      min_kols: z.number().min(1).max(20).default(1).describe("Minimum KOL buyers to include a token"),
      limit: z.number().min(1).max(50).default(20).describe("Number of hot tokens to return"),
      min_avg_winrate: z.number().optional().describe("PRO+: require avg winrate_7d of buyers >= N (0-100)"),
      unique_strategies: z.number().optional().describe("PRO+: require >= N distinct strategies among buyers"),
    },
  • src/index.ts:236-253 (registration)
    Tool registration via server.tool('madeonsol_kol_hot_tokens', ...) inside the registerTools function.
    server.tool(
      "madeonsol_kol_hot_tokens",
      "KOL momentum tokens — tokens with accelerating KOL buy interest, early signals before coordination triggers. PRO+ adds buyer-quality filters.",
      {
        period: z.enum(["1h", "6h"]).default("6h").describe("Time period: 1h or 6h"),
        min_kols: z.number().min(1).max(20).default(1).describe("Minimum KOL buyers to include a token"),
        limit: z.number().min(1).max(50).default(20).describe("Number of hot tokens to return"),
        min_avg_winrate: z.number().optional().describe("PRO+: require avg winrate_7d of buyers >= N (0-100)"),
        unique_strategies: z.number().optional().describe("PRO+: require >= N distinct strategies among buyers"),
      },
      readOnlyAnnotations,
      async ({ period, min_kols, limit, min_avg_winrate, unique_strategies }) => {
        const params: Record<string, string | number> = { period, min_kols, limit };
        if (min_avg_winrate !== undefined) params.min_avg_winrate = min_avg_winrate;
        if (unique_strategies !== undefined) params.unique_strategies = unique_strategies;
        return { content: [{ type: "text" as const, text: await query("/api/x402/kol/tokens/hot", params) }] };
      }
    );
  • The query() helper function used by the handler to make authenticated API calls to the MadeOnSol backend.
    async function query(path: string, params?: Record<string, string | number>) {
      // API key uses /api/v1/ endpoints; x402 uses /api/x402/
      const apiPath = authMode === "x402" || authMode === "none"
        ? path
        : path.replace("/api/x402/", "/api/v1/");
      const url = new URL(apiPath, BASE_URL);
      if (params) {
        for (const [k, v] of Object.entries(params)) {
          if (v !== undefined) url.searchParams.set(k, String(v));
        }
      }
      const headers = apiKeyHeaders();
      const res = authMode === "x402"
        ? await paidFetch(url.toString())
        : await fetch(url.toString(), { headers });
      if (!res.ok) {
        const body = await res.text().catch(() => "");
        return `Error ${res.status}: ${body}`;
      }
      return JSON.stringify(await res.json(), null, 2);
    }
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds context about PRO+ filters but does not disclose additional behavioral traits such as rate limits, pagination, or handling of empty results.

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?

The description is two sentences, front-loaded with the core purpose, and efficiently conveys the tool's value and the PRO+ enhancement. No wasted words.

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

Completeness3/5

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

Given 5 optional parameters, no output schema, and moderate complexity, the description covers the essential idea but lacks details on how 'accelerating' is measured or the format of returned data. It is adequate but could be more comprehensive.

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% with property descriptions. The description adds value by explaining that 'min_avg_winrate' and 'unique_strategies' are PRO+ features, providing context beyond the schema.

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 clearly identifies the tool as returning tokens with accelerating KOL buy interest, positioning it as early signals. It uses specific terms like 'momentum' and 'accelerating', which distinguishes it from sibling tools like 'madeonsol_kol_trending_tokens'.

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 implies usage for early detection ('before coordination triggers'), but does not explicitly state when to use this tool over alternatives or when not to use it. No exclusion criteria are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LamboPoewert/mcp-server-madeonsol'

If you have feedback or need assistance with the MCP directory API, please join our Discord server