Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_kol_compare_wallets

Read-onlyIdempotent

Compare 2-5 KOL wallets side-by-side by strategy, winrates, ROI, and percentile. PRO+ reveals tokens bought by multiple wallets in the last 30 days.

Instructions

Side-by-side comparison of 2-5 KOL wallets — strategy, winrates, ROI, percentile. PRO+ adds 30d overlap tokens (bought by 2+ of the wallets).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletsYes2-5 wallet addresses. BASIC=2, PRO=4, ULTRA=5.

Implementation Reference

  • src/index.ts:268-278 (registration)
    The tool is registered with the MCP server under the name 'madeonsol_kol_compare_wallets'. It accepts 2-5 wallet addresses as an array of strings via Zod schema validation.
    server.tool(
      "madeonsol_kol_compare_wallets",
      "Side-by-side comparison of 2-5 KOL wallets — strategy, winrates, ROI, percentile. PRO+ adds 30d overlap tokens (bought by 2+ of the wallets).",
      {
        wallets: z.array(z.string()).min(2).max(5).describe("2-5 wallet addresses. BASIC=2, PRO=4, ULTRA=5."),
      },
      readOnlyAnnotations,
      async ({ wallets }) => ({
        content: [{ type: "text" as const, text: await query("/api/x402/kol/compare", { wallets: wallets.join(",") }) }],
      })
    );
  • The handler function joins the wallets array into a comma-separated string and calls the query() helper which proxies the request to the MadeOnSol API endpoint /api/x402/kol/compare. The response is returned as text content.
      async ({ wallets }) => ({
        content: [{ type: "text" as const, text: await query("/api/x402/kol/compare", { wallets: wallets.join(",") }) }],
      })
    );
  • The input schema uses Zod to validate a 'wallets' parameter: an array of strings with a minimum of 2 and maximum of 5 entries.
    {
      wallets: z.array(z.string()).min(2).max(5).describe("2-5 wallet addresses. BASIC=2, PRO=4, ULTRA=5."),
    },
  • The query() helper function is used by the handler to make HTTP requests to the MadeOnSol API. It handles auth-mode-based routing (x402 vs api/v1), constructs URLs with params, and returns JSON-stringified responses.
    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?

The description adds significant context beyond annotations by detailing the output content (metrics compared and PRO+ overlap tokens). Annotations already indicate readOnlyHint and idempotentHint, so the behavioral disclosure is adequately enhanced.

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 concise sentences, front-loaded with the core function, and every sentence adds value. No filler or redundancy.

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?

Given no output schema, the description adequately explains what the tool returns (comparison metrics and optional overlap tokens). It omits format details but covers essential outcome. Annotations provide safety context, so overall completeness is good.

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?

The input schema already provides a description for the 'wallets' parameter (count limits by plan). The description repeats the count range and adds plan-dependent behavior (PRO+ overlap tokens), adding marginal value over 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 specifies the tool's function: side-by-side comparison of 2-5 KOL wallets, listing specific metrics (strategy, winrates, ROI, percentile) and an additional PRO+ feature. This distinguishes it from sibling tools like madeonsol_kol_leaderboard or madeonsol_kol_pnl.

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 comparing multiple KOL wallets but does not explicitly state when to use this tool versus alternatives. No when-not or exclusions are provided, though the plan-based feature (PRO+) offers some context on limitations.

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