Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_kol_pnl

Read-onlyIdempotent

Get per-wallet PnL breakdown for Solana KOLs: realized PnL, win rate, profit factor, max drawdown, daily equity curve, and closed/open positions. Input a wallet address and time period to evaluate trading performance.

Instructions

Deep per-wallet PnL breakdown — realized PnL, win rate, profit factor, max drawdown, daily equity curve, closed/open positions. BASIC: summary only. PRO: + curve + closed. ULTRA: + open positions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletYesKOL wallet address (base58)
periodNoTime period for PnL calculation30d

Implementation Reference

  • Handler: The tool handler for madeonsol_kol_pnl. It accepts a wallet (base58) and period (7d/30d/90d/180d). If authMode is 'madeonsol' (API key), it fetches from GET /api/v1/kol/{wallet}/pnl?period={period}; otherwise returns an error message saying a MadeOnSol API key is required.
    server.tool(
      "madeonsol_kol_pnl",
      "Deep per-wallet PnL breakdown — realized PnL, win rate, profit factor, max drawdown, daily equity curve, closed/open positions. BASIC: summary only. PRO: + curve + closed. ULTRA: + open positions.",
      {
        wallet: z.string().describe("KOL wallet address (base58)"),
        period: z.enum(["7d", "30d", "90d", "180d"]).default("30d").describe("Time period for PnL calculation"),
      },
      readOnlyAnnotations,
      async ({ wallet, period }) => {
        if (authMode === "madeonsol") {
          const headers: Record<string, string> = { ...apiKeyHeaders() };
          const res = await fetch(`${BASE_URL}/api/v1/kol/${wallet}/pnl?period=${period}`, { headers });
          if (!res.ok) { const body = await res.text().catch(() => ""); return { content: [{ type: "text" as const, text: `Error ${res.status}: ${body}` }] }; }
          return { content: [{ type: "text" as const, text: JSON.stringify(await res.json(), null, 2) }] };
        }
        return { content: [{ type: "text" as const, text: "KOL PnL requires MADEONSOL_API_KEY (msk_) — get one free at madeonsol.com/pricing." }] };
      }
    );
  • Schema: Input validation for madeonsol_kol_pnl using Zod. Accepts 'wallet' (base58 string, required) and 'period' (enum of 7d/30d/90d/180d, default '30d').
    "madeonsol_kol_pnl",
    "Deep per-wallet PnL breakdown — realized PnL, win rate, profit factor, max drawdown, daily equity curve, closed/open positions. BASIC: summary only. PRO: + curve + closed. ULTRA: + open positions.",
    {
      wallet: z.string().describe("KOL wallet address (base58)"),
      period: z.enum(["7d", "30d", "90d", "180d"]).default("30d").describe("Time period for PnL calculation"),
    },
    readOnlyAnnotations,
  • src/index.ts:298-298 (registration)
    Registration: The tool named 'madeonsol_kol_pnl' is registered via server.tool() call within the registerTools function in src/index.ts. No separate registration file exists; all tools are registered inline.
    server.tool(
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable context about tier-dependent output (BASIC, PRO, ULTRA) and specific metrics (realized PnL, win rate, etc.), which annotates the behavior beyond the 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 long, front-loads the primary purpose, and every sentence adds value (first states purpose and metrics, second explains tier differences). No fluff.

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 lists key metrics but does not specify return format or error conditions. However, annotations cover safety (read-only, idempotent), and parameters are simple. It is complete enough for a typical read tool, though a note on response shape would improve it.

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 description coverage is 100%, with both 'wallet' and 'period' described in the schema. The description does not add new semantic information about the parameters; it simply restates the purpose. A score of 3 is baseline given high schema coverage.

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 'Deep per-wallet PnL breakdown' with specific metrics listed, and it distinguishes from sibling tools—none of which focus on PnL breakdown. The verb 'break down' plus resource 'PnL' is precise.

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 does not provide explicit guidance on when to use this tool versus alternatives. It implies usage for wallet PnL analysis but lacks exclusion criteria or comparison to siblings like madeonsol_kol_leaderboard or madeonsol_kol_compare_wallets.

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