Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_deployer_alerts

Read-onlyIdempotent

Get real-time Pump.fun deployer alerts enriched with KOL buy data. Filter by deployer tier, alert type, priority, or minimum KOL buys to reduce noise.

Instructions

Get real-time alerts from Pump.fun deployers with KOL buy enrichment. Filters: deployer tier, alert_type, priority, and min_kol_buys to gate out noise. Cursor-paginated via 'before' (preferred over 'offset' at scale).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of deployer alerts to return (1-100)
offsetNoLegacy offset pagination (prefer 'before' for polling)
beforeNoCursor — ISO 8601 timestamp; returns alerts strictly older than this. Pass next_before from the previous response.
sinceNoOnly alerts after this ISO 8601 timestamp.
tierNoFilter by deployer tier. PRO/ULTRA only — BASIC callers receive HTTP 403.
alert_typeNoFilter by alert_type (e.g. 'new_deploy', 'bonded').
priorityNoFilter by alert priority.
min_kol_buysNoOnly alerts where at least N KOLs bought the token (1-100).

Implementation Reference

  • src/index.ts:159-183 (registration)
    Registration of the 'madeonsol_deployer_alerts' tool on the MCP server via server.tool(), including input schema (Zod) and the handler function.
    server.tool(
      "madeonsol_deployer_alerts",
      "Get real-time alerts from Pump.fun deployers with KOL buy enrichment. Filters: deployer tier, alert_type, priority, and min_kol_buys to gate out noise. Cursor-paginated via 'before' (preferred over 'offset' at scale).",
      {
        limit: z.number().min(1).max(100).default(10).describe("Number of deployer alerts to return (1-100)"),
        offset: z.number().min(0).default(0).describe("Legacy offset pagination (prefer 'before' for polling)"),
        before: z.string().optional().describe("Cursor — ISO 8601 timestamp; returns alerts strictly older than this. Pass next_before from the previous response."),
        since: z.string().optional().describe("Only alerts after this ISO 8601 timestamp."),
        tier: z.enum(["elite", "good", "moderate", "rising", "cold"]).optional().describe("Filter by deployer tier. PRO/ULTRA only — BASIC callers receive HTTP 403."),
        alert_type: z.string().optional().describe("Filter by alert_type (e.g. 'new_deploy', 'bonded')."),
        priority: z.enum(["high", "medium", "low"]).optional().describe("Filter by alert priority."),
        min_kol_buys: z.number().min(1).max(100).optional().describe("Only alerts where at least N KOLs bought the token (1-100)."),
      },
      readOnlyAnnotations,
      async ({ limit, offset, before, since, tier, alert_type, priority, min_kol_buys }) => {
        const params: Record<string, string | number> = { limit, offset };
        if (before) params.before = before;
        if (since) params.since = since;
        if (tier) params.tier = tier;
        if (alert_type) params.alert_type = alert_type;
        if (priority) params.priority = priority;
        if (min_kol_buys !== undefined) params.min_kol_buys = min_kol_buys;
        return { content: [{ type: "text" as const, text: await query("/api/x402/deployer-hunter/alerts", params) }] };
      }
    );
  • Handler function that constructs the API request parameters and calls the query() helper to fetch deployer alerts from the backend.
    async ({ limit, offset, before, since, tier, alert_type, priority, min_kol_buys }) => {
      const params: Record<string, string | number> = { limit, offset };
      if (before) params.before = before;
      if (since) params.since = since;
      if (tier) params.tier = tier;
      if (alert_type) params.alert_type = alert_type;
      if (priority) params.priority = priority;
      if (min_kol_buys !== undefined) params.min_kol_buys = min_kol_buys;
      return { content: [{ type: "text" as const, text: await query("/api/x402/deployer-hunter/alerts", params) }] };
    }
  • Input schema defined with Zod — validates limit (1-100, default 10), offset (default 0), before cursor, since timestamp, tier enum, alert_type string, priority enum, and min_kol_buys number.
    {
      limit: z.number().min(1).max(100).default(10).describe("Number of deployer alerts to return (1-100)"),
      offset: z.number().min(0).default(0).describe("Legacy offset pagination (prefer 'before' for polling)"),
      before: z.string().optional().describe("Cursor — ISO 8601 timestamp; returns alerts strictly older than this. Pass next_before from the previous response."),
      since: z.string().optional().describe("Only alerts after this ISO 8601 timestamp."),
      tier: z.enum(["elite", "good", "moderate", "rising", "cold"]).optional().describe("Filter by deployer tier. PRO/ULTRA only — BASIC callers receive HTTP 403."),
      alert_type: z.string().optional().describe("Filter by alert_type (e.g. 'new_deploy', 'bonded')."),
      priority: z.enum(["high", "medium", "low"]).optional().describe("Filter by alert priority."),
      min_kol_buys: z.number().min(1).max(100).optional().describe("Only alerts where at least N KOLs bought the token (1-100)."),
    },
  • The query() helper function used by the handler to make the actual HTTP request to the MadeOnSol API (either /api/x402/ or /api/v1/ depending on auth mode).
    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 indicate read-only, non-destructive, idempotent behavior. The description adds value by explaining KOL enrichment, filter purpose ('gate out noise'), and pagination preference (cursor over offset), providing context beyond structured fields.

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 with no redundancy. The first sentence covers purpose and enrichment; the second details filters and pagination. Every sentence earns its place.

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 tool with 8 parameters and no output schema, the description covers the main purpose, key filters, pagination method, and enrichment. It is complete enough for an agent to understand usage, though output format details are absent.

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%, so baseline is 3. The description summarizes filters and pagination but does not add significant semantic detail beyond what the schema already provides.

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 verb 'Get' and the resource 'real-time alerts from Pump.fun deployers with KOL buy enrichment', distinguishing this tool from siblings that focus on other aspects like deployer trajectories or KOL alerts.

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 provides implicit usage context via filters and pagination, but lacks explicit when-to-use or when-not-to-use guidance compared to sibling tools such as madeonsol_kol_alerts_recent or madeonsol_deployer_trajectory.

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