Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_coordination_alerts_create

Set up coordination alert rules triggered within 1 second when KOL clusters meet density thresholds. Alerts delivered via WebSocket or HMAC-signed webhook.

Instructions

Create a coordination alert rule. Fires within ~1s when a KOL cluster meets thresholds (peak-density scored). Delivered via WebSocket (kol:coordination channel) and/or HMAC-signed webhook. Returns webhook_secret ONCE when delivery_mode includes 'webhook' — store it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional label
min_kolsNoMinimum distinct KOLs in the window (default 3)
window_minutesNoPeak-density window size in minutes (default 15)
min_scoreNoMinimum composite score 0-100 (default 60)
include_majorsNoInclude WIF/BONK/POPCAT etc. Default false.
cooldown_minNoSilence per (rule, token) in minutes (default 60)
score_jump_breakNoRe-fire early when score jumps by N points vs last fire (default 10)
delivery_modeNoWhere to deliver fires
webhook_urlNoRequired when delivery_mode includes 'webhook'

Implementation Reference

  • Handler function for madeonsol_coordination_alerts_create tool. Builds request body from args and sends POST to /kol/coordination/alerts via the restQuery helper.
    server.tool(
      "madeonsol_coordination_alerts_create",
      "Create a coordination alert rule. Fires within ~1s when a KOL cluster meets thresholds (peak-density scored). Delivered via WebSocket (kol:coordination channel) and/or HMAC-signed webhook. Returns webhook_secret ONCE when delivery_mode includes 'webhook' — store it.",
      {
        name: z.string().optional().describe("Optional label"),
        min_kols: z.number().min(2).max(50).optional().describe("Minimum distinct KOLs in the window (default 3)"),
        window_minutes: z.number().min(1).max(60).optional().describe("Peak-density window size in minutes (default 15)"),
        min_score: z.number().min(0).max(100).optional().describe("Minimum composite score 0-100 (default 60)"),
        include_majors: z.boolean().optional().describe("Include WIF/BONK/POPCAT etc. Default false."),
        cooldown_min: z.number().min(1).optional().describe("Silence per (rule, token) in minutes (default 60)"),
        score_jump_break: z.number().min(1).max(100).optional().describe("Re-fire early when score jumps by N points vs last fire (default 10)"),
        delivery_mode: z.enum(["websocket", "webhook", "both"]).optional().describe("Where to deliver fires"),
        webhook_url: z.string().url().optional().describe("Required when delivery_mode includes 'webhook'"),
      },
      { readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: true },
      async (args) => {
        const body: Record<string, unknown> = {};
        for (const [k, v] of Object.entries(args)) if (v !== undefined) body[k] = v;
        return { content: [{ type: "text" as const, text: await restQuery("POST", "/kol/coordination/alerts", body) }] };
      }
    );
  • Input schema for madeonsol_coordination_alerts_create: name, min_kols, window_minutes, min_score, include_majors, cooldown_min, score_jump_break, delivery_mode, webhook_url.
    "madeonsol_coordination_alerts_create",
    "Create a coordination alert rule. Fires within ~1s when a KOL cluster meets thresholds (peak-density scored). Delivered via WebSocket (kol:coordination channel) and/or HMAC-signed webhook. Returns webhook_secret ONCE when delivery_mode includes 'webhook' — store it.",
    {
      name: z.string().optional().describe("Optional label"),
      min_kols: z.number().min(2).max(50).optional().describe("Minimum distinct KOLs in the window (default 3)"),
      window_minutes: z.number().min(1).max(60).optional().describe("Peak-density window size in minutes (default 15)"),
      min_score: z.number().min(0).max(100).optional().describe("Minimum composite score 0-100 (default 60)"),
      include_majors: z.boolean().optional().describe("Include WIF/BONK/POPCAT etc. Default false."),
      cooldown_min: z.number().min(1).optional().describe("Silence per (rule, token) in minutes (default 60)"),
      score_jump_break: z.number().min(1).max(100).optional().describe("Re-fire early when score jumps by N points vs last fire (default 10)"),
      delivery_mode: z.enum(["websocket", "webhook", "both"]).optional().describe("Where to deliver fires"),
      webhook_url: z.string().url().optional().describe("Required when delivery_mode includes 'webhook'"),
    },
  • src/index.ts:788-808 (registration)
    Tool registration via server.tool() for madeonsol_coordination_alerts_create. Registered conditionally inside the hasRestAuth block (requires MADEONSOL_API_KEY).
    server.tool(
      "madeonsol_coordination_alerts_create",
      "Create a coordination alert rule. Fires within ~1s when a KOL cluster meets thresholds (peak-density scored). Delivered via WebSocket (kol:coordination channel) and/or HMAC-signed webhook. Returns webhook_secret ONCE when delivery_mode includes 'webhook' — store it.",
      {
        name: z.string().optional().describe("Optional label"),
        min_kols: z.number().min(2).max(50).optional().describe("Minimum distinct KOLs in the window (default 3)"),
        window_minutes: z.number().min(1).max(60).optional().describe("Peak-density window size in minutes (default 15)"),
        min_score: z.number().min(0).max(100).optional().describe("Minimum composite score 0-100 (default 60)"),
        include_majors: z.boolean().optional().describe("Include WIF/BONK/POPCAT etc. Default false."),
        cooldown_min: z.number().min(1).optional().describe("Silence per (rule, token) in minutes (default 60)"),
        score_jump_break: z.number().min(1).max(100).optional().describe("Re-fire early when score jumps by N points vs last fire (default 10)"),
        delivery_mode: z.enum(["websocket", "webhook", "both"]).optional().describe("Where to deliver fires"),
        webhook_url: z.string().url().optional().describe("Required when delivery_mode includes 'webhook'"),
      },
      { readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: true },
      async (args) => {
        const body: Record<string, unknown> = {};
        for (const [k, v] of Object.entries(args)) if (v !== undefined) body[k] = v;
        return { content: [{ type: "text" as const, text: await restQuery("POST", "/kol/coordination/alerts", body) }] };
      }
    );
  • restQuery helper used by the handler to make authenticated REST API calls to MadeOnSol's API.
    const hasRestAuth = authMode === "madeonsol";
    if (hasRestAuth) {
      async function restQuery(method: string, path: string, body?: unknown): Promise<string> {
        const headers: Record<string, string> = {
          "Content-Type": "application/json",
          ...apiKeyHeaders(),
        };
        const res = await fetch(`${BASE_URL}/api/v1${path}`, {
          method,
          headers,
          ...(body ? { body: JSON.stringify(body) } : {}),
        });
        if (!res.ok) {
          const text = await res.text().catch(() => "");
          return `Error ${res.status}: ${text}`;
        }
        return JSON.stringify(await res.json(), null, 2);
      }
Behavior4/5

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

Adds key behavioral details: ~1s latency, WebSocket delivery, HMAC-signed webhook, one-time return of webhook_secret. Annotations (readOnlyHint=false, destructiveHint=false) are consistent; description enhances transparency.

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?

Three sentences, each essential. First sentence states purpose, second describes triggers and delivery, third explains output handling. No wasted words.

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?

No output schema, but description explains key output (webhook_secret once) and behavior. Could mention error conditions or prerequisites, but adequate for creation tool.

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 has 100% coverage; description adds context about delivery modes and the one-time webhook_secret behavior, which are not in schema descriptions. Adds value beyond 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?

Clear verb+resource: 'Create a coordination alert rule'. Immediately distinguishes from sibling tools like delete, get, list, update.

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?

Describes when to use (creation) and provides details on delivery modes, but not explicit exclusions or alternatives; however, sibling context makes it clear.

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