Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_token_cap_table

Read-onlyIdempotent

Retrieve cap table for a Solana token, showing non-deployer early buyers with profit/loss, KOL identity, and bot flags. Use token mint address.

Instructions

First non-deployer early buyers for a token, enriched with PnL, KOL identity, and bot flags. PRO=top 10 (truncated wallets), ULTRA=top 20 (full). BASIC: 403.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintYesToken mint address (base58)

Implementation Reference

  • Tool handler: makes an HTTP GET request to the MadeOnSol API endpoint /api/v1/tokens/{mint}/cap-table using the restQuery helper, returning first non-deployer early buyers for a token, enriched with PnL, KOL identity, and bot flags.
    server.tool(
      "madeonsol_token_cap_table",
      "First non-deployer early buyers for a token, enriched with PnL, KOL identity, and bot flags. PRO=top 10 (truncated wallets), ULTRA=top 20 (full). BASIC: 403.",
      { mint: z.string().describe("Token mint address (base58)") },
      { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      async ({ mint }) => ({
        content: [{ type: "text" as const, text: await restQuery("GET", `/tokens/${encodeURIComponent(mint)}/cap-table`) }],
      })
    );
  • Input schema: accepts a single required parameter 'mint' (base58 token mint address) validated with Zod.
    { mint: z.string().describe("Token mint address (base58)") },
    { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
  • src/index.ts:624-632 (registration)
    Tool registration via server.tool() with the name 'madeonsol_token_cap_table', description, schema, annotations, and handler. Registered conditionally when authMode is 'madeonsol' (i.e., MADEONSOL_API_KEY is set).
    server.tool(
      "madeonsol_token_cap_table",
      "First non-deployer early buyers for a token, enriched with PnL, KOL identity, and bot flags. PRO=top 10 (truncated wallets), ULTRA=top 20 (full). BASIC: 403.",
      { mint: z.string().describe("Token mint address (base58)") },
      { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      async ({ mint }) => ({
        content: [{ type: "text" as const, text: await restQuery("GET", `/tokens/${encodeURIComponent(mint)}/cap-table`) }],
      })
    );
  • Helper function restQuery used by the handler to make authenticated HTTP requests to the MadeOnSol API. Prepends /api/v1 to the path and handles errors.
    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?

Annotations mark as read-only/idempotent. Description adds tier-based access restrictions ('PRO=top 10 truncated, ULTRA=top 20 full, BASIC: 403'), indicating different responses per plan, and filters out deployer wallets. This is valuable beyond annotations.

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?

Two concise sentences, front-loaded with core purpose, followed by tier details. No waste.

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?

Describes returned data (PnL, KOL identity, bot flags) and tier variations. However, 'BASIC: 403' is ambiguous (rejection? error? unclear). No output schema exists, so description mostly suffices but could clarify the BASIC behavior.

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 covers the single parameter 'mint' with description 'Token mint address (base58)'. Description does not add further meaning; baseline 3 is appropriate.

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 returns 'first non-deployer early buyers for a token, enriched with PnL, KOL identity, and bot flags', and specifies output levels by tier (PRO/ULTRA/BASIC). It distinguishes itself from siblings by focusing on early buyer enrichment, a unique aspect.

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?

No explicit guidance on when to use this tool versus alternatives like madeonsol_token_buyer_quality. Usage is implied by its focus on early buyers, but no exclusions or context are 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