Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_kol_alerts_recent

Read-onlyIdempotent

Retrieve real-time KOL alerts including consensus clusters, fresh-token buys, and heating-up wallets. Filter by time window, alert type, and severity.

Instructions

Live KOL alert feed — consensus clusters, fresh-token KOL buys, and heating-up wallets in one unified stream.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNoLookback window15m
typesNoFilter to specific alert types
min_severityNoMinimum severity to include
limitNoMax alerts to return

Implementation Reference

  • src/index.ts:280-296 (registration)
    Tool registration for 'madeonsol_kol_alerts_recent' via server.tool() with schema definition and handler.
    server.tool(
      "madeonsol_kol_alerts_recent",
      "Live KOL alert feed — consensus clusters, fresh-token KOL buys, and heating-up wallets in one unified stream.",
      {
        window: z.enum(["5m", "15m", "1h", "6h", "24h"]).default("15m").describe("Lookback window"),
        types: z.array(z.enum(["consensus_cluster", "fresh_token_kol_buy", "heating_up"])).optional().describe("Filter to specific alert types"),
        min_severity: z.enum(["low", "medium", "high"]).optional().describe("Minimum severity to include"),
        limit: z.number().min(1).max(200).default(50).describe("Max alerts to return"),
      },
      readOnlyAnnotations,
      async ({ window, types, min_severity, limit }) => {
        const params: Record<string, string | number> = { window, limit };
        if (types && types.length > 0) params.types = types.join(",");
        if (min_severity) params.min_severity = min_severity;
        return { content: [{ type: "text" as const, text: await query("/api/x402/kol/alerts/recent", params) }] };
      }
    );
  • Input schema using Zod: window (enum 5m/15m/1h/6h/24h default 15m), types (optional array of alert types), min_severity (optional low/medium/high), limit (1-200 default 50).
    {
      window: z.enum(["5m", "15m", "1h", "6h", "24h"]).default("15m").describe("Lookback window"),
      types: z.array(z.enum(["consensus_cluster", "fresh_token_kol_buy", "heating_up"])).optional().describe("Filter to specific alert types"),
      min_severity: z.enum(["low", "medium", "high"]).optional().describe("Minimum severity to include"),
      limit: z.number().min(1).max(200).default(50).describe("Max alerts to return"),
    },
  • Handler function that builds query params and calls the shared query() helper with endpoint /api/x402/kol/alerts/recent.
    async ({ window, types, min_severity, limit }) => {
      const params: Record<string, string | number> = { window, limit };
      if (types && types.length > 0) params.types = types.join(",");
      if (min_severity) params.min_severity = min_severity;
      return { content: [{ type: "text" as const, text: await query("/api/x402/kol/alerts/recent", params) }] };
    }
  • Shared query() helper used by the handler — builds URL with auth-mode-aware path rewriting (x402 vs v1), attaches headers, executes fetch, and returns JSON.
    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);
    }
Behavior4/5

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

Annotations already specify readOnlyHint=true, idempotentHint=true, and openWorldHint=true. The description adds 'live' and 'unified stream', providing useful context beyond annotations. No contradictions.

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 a single, well-structured sentence that communicates the core purpose without redundancy or extraneous information.

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?

No output schema is provided, and the description does not explain the return format, ordering, or pagination. With many sibling tools, more context about what the agent can expect would be beneficial.

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% with each parameter well-described. The description reinforces the alert types from the 'types' enum but does not add new semantic details beyond the schema.

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 'Live KOL alert feed' and enumerates three specific alert types (consensus clusters, fresh-token KOL buys, heating-up wallets), distinguishing it from sibling tools like madeonsol_kol_feed or madeonsol_kol_coordination.

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 use for real-time alerts but offers no explicit guidance on when to choose this tool over alternatives like madeonsol_kol_feed or madeonsol_deployer_alerts. The agent must infer usage from context.

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