Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_kol_feed

Read-onlyIdempotent

Fetch real-time Solana KOL trades from 1000+ tracked wallets with market cap at trade time. Supports filtering by trade type, wallet, and PRO+ parameters like size, token age, strategy, and winrate.

Instructions

Get real-time Solana KOL trades from 1,000+ tracked wallets. Each trade includes the token's market cap (USD) at the moment of trade — sourced from our in-memory price tracker, accurate to the millisecond, faster than Dexscreener spot. PRO+ adds size/age/strategy/winrate filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of trades to return (1-100)
beforeNoCursor — ISO 8601 timestamp; returns trades strictly older than this. Pass next_before from the previous response for polling.
actionNoFilter by trade type: buy or sell
kolNoFilter by specific KOL wallet address (base58)
min_solNoPRO+: minimum SOL size per trade
token_age_max_minNoPRO+: max token age in minutes at time of trade
exclude_sellsNoPRO+: drop sell-side trades
min_kol_winrateNoPRO+: minimum 7d winrate of the KOL (0-100)
strategyNoPRO+: filter by auto-tagged strategy

Implementation Reference

  • src/index.ts:85-112 (registration)
    Tool registration using server.tool() with name 'madeonsol_kol_feed', description, Zod schema params, annotations, and async handler.
    server.tool(
      "madeonsol_kol_feed",
      "Get real-time Solana KOL trades from 1,000+ tracked wallets. Each trade includes the token's market cap (USD) at the moment of trade — sourced from our in-memory price tracker, accurate to the millisecond, faster than Dexscreener spot. PRO+ adds size/age/strategy/winrate filters.",
      {
        limit: z.number().min(1).max(100).default(10).describe("Number of trades to return (1-100)"),
        before: z.string().optional().describe("Cursor — ISO 8601 timestamp; returns trades strictly older than this. Pass next_before from the previous response for polling."),
        action: z.enum(["buy", "sell"]).optional().describe("Filter by trade type: buy or sell"),
        kol: z.string().optional().describe("Filter by specific KOL wallet address (base58)"),
        min_sol: z.number().optional().describe("PRO+: minimum SOL size per trade"),
        token_age_max_min: z.number().optional().describe("PRO+: max token age in minutes at time of trade"),
        exclude_sells: z.boolean().optional().describe("PRO+: drop sell-side trades"),
        min_kol_winrate: z.number().optional().describe("PRO+: minimum 7d winrate of the KOL (0-100)"),
        strategy: z.enum(["scalper", "day_trader", "swing_trader", "hodler", "mixed"]).optional().describe("PRO+: filter by auto-tagged strategy"),
      },
      readOnlyAnnotations,
      async ({ limit, before, action, kol, min_sol, token_age_max_min, exclude_sells, min_kol_winrate, strategy }) => {
        const params: Record<string, string | number> = { limit };
        if (before) params.before = before;
        if (action) params.action = action;
        if (kol) params.kol = kol;
        if (min_sol !== undefined) params.min_sol = min_sol;
        if (token_age_max_min !== undefined) params.token_age_max_min = token_age_max_min;
        if (exclude_sells) params.exclude_sells = "true";
        if (min_kol_winrate !== undefined) params.min_kol_winrate = min_kol_winrate;
        if (strategy) params.strategy = strategy;
        return { content: [{ type: "text" as const, text: await query("/api/x402/kol/feed", params) }] };
      }
    );
  • Zod schema defining input validation: limit (1-100, default 10), before (ISO cursor), action (buy/sell), kol, min_sol, token_age_max_min, exclude_sells, min_kol_winrate, and strategy.
    {
      limit: z.number().min(1).max(100).default(10).describe("Number of trades to return (1-100)"),
      before: z.string().optional().describe("Cursor — ISO 8601 timestamp; returns trades strictly older than this. Pass next_before from the previous response for polling."),
      action: z.enum(["buy", "sell"]).optional().describe("Filter by trade type: buy or sell"),
      kol: z.string().optional().describe("Filter by specific KOL wallet address (base58)"),
      min_sol: z.number().optional().describe("PRO+: minimum SOL size per trade"),
      token_age_max_min: z.number().optional().describe("PRO+: max token age in minutes at time of trade"),
      exclude_sells: z.boolean().optional().describe("PRO+: drop sell-side trades"),
      min_kol_winrate: z.number().optional().describe("PRO+: minimum 7d winrate of the KOL (0-100)"),
      strategy: z.enum(["scalper", "day_trader", "swing_trader", "hodler", "mixed"]).optional().describe("PRO+: filter by auto-tagged strategy"),
    },
  • Handler: builds a params object from incoming args, then calls query('/api/x402/kol/feed', params) and returns the result as text content.
      async ({ limit, before, action, kol, min_sol, token_age_max_min, exclude_sells, min_kol_winrate, strategy }) => {
        const params: Record<string, string | number> = { limit };
        if (before) params.before = before;
        if (action) params.action = action;
        if (kol) params.kol = kol;
        if (min_sol !== undefined) params.min_sol = min_sol;
        if (token_age_max_min !== undefined) params.token_age_max_min = token_age_max_min;
        if (exclude_sells) params.exclude_sells = "true";
        if (min_kol_winrate !== undefined) params.min_kol_winrate = min_kol_winrate;
        if (strategy) params.strategy = strategy;
        return { content: [{ type: "text" as const, text: await query("/api/x402/kol/feed", params) }] };
      }
    );
  • The query() helper function used by the handler — builds the URL with params, adds auth headers, performs the fetch (with x402 payment integration if applicable), and returns JSON string or error text.
    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, and openWorldHint=true. The description adds context about real-time data from an in-memory price tracker with millisecond accuracy and mentions PRO+ filters, but does not disclose rate limits or any limitations. It adds some value beyond annotations but is not comprehensive.

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 concise (two sentences), front-loaded with the core purpose in the first sentence, and uses the second sentence to add context about speed and PRO+ features. Every sentence earns its place without 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?

With 9 parameters and no output schema, the description provides the key output detail (market cap at trade time) but omits the full structure of returned trades. While annotations are good, more detail on the response format would improve completeness for an agent.

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 all 9 parameters described in the input schema. The description mentions PRO+ filters for some parameters but adds no additional meaning to the schema descriptions. Baseline score of 3 is appropriate since the schema already does the heavy lifting.

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 it retrieves real-time KOL trades from over 1,000 tracked wallets, with market cap data. This distinguishes it from sibling tools like madeonsol_kol_hot_tokens or madeonsol_kol_leaderboard, which serve different purposes.

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 real-time trade monitoring and mentions speed advantages, but does not explicitly state when to use this tool versus alternatives like madeonsol_kol_alerts_recent or madeonsol_kol_hot_tokens. No when-not-to-use guidance is 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