Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_alpha_linked

Read-onlyIdempotent

Identify wallets that co-purchased 3+ tokens within 2 seconds of a target wallet on Solana. ULTRA tier required.

Instructions

Wallets behaviorally linked to a target wallet (co-bought 3+ tokens within 2 seconds). ULTRA only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletYesWallet address (base58)

Implementation Reference

  • src/index.ts:612-619 (registration)
    Tool registration — 'madeonsol_alpha_linked' is registered via server.tool() with its schema and handler handler
    server.tool(
      "madeonsol_alpha_linked",
      "Wallets behaviorally linked to a target wallet (co-bought 3+ tokens within 2 seconds). ULTRA only.",
      { wallet: z.string().describe("Wallet address (base58)") },
      { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      async ({ wallet }) => ({
        content: [{ type: "text" as const, text: await restQuery("GET", `/alpha/${encodeURIComponent(wallet)}/linked`) }],
      })
  • Input schema — accepts single 'wallet' param (base58 address)
    { wallet: z.string().describe("Wallet address (base58)") },
    { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
  • Handler function — makes GET request to /alpha/{wallet}/linked REST endpoint via restQuery helper
    async ({ wallet }) => ({
      content: [{ type: "text" as const, text: await restQuery("GET", `/alpha/${encodeURIComponent(wallet)}/linked`) }],
    })
  • Helper function 'restQuery' — used by the handler to make authenticated REST API calls to MadeOnSol
    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);
    }
  • src/index.ts:1055-1055 (registration)
    Tool listed in server card metadata (.well-known/mcp/server-card.json)
    { name: "madeonsol_alpha_linked", description: "Behaviorally linked wallets (co-bought 3+ tokens within 2s). ULTRA only." },
Behavior4/5

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

Annotations already show readOnly, idempotent; description adds specific behavioral context (co-buying heuristic, time window). No contradiction with 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?

Single sentence, front-loaded with key info, no filler words.

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?

Explains linkage condition well, but lacks expected output format (likely a list of wallets). Adequate for a simple tool with one input and no output schema.

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 provides full description of 'wallet' parameter; description does not add extra meaning beyond listing the linkage criteria.

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?

Clearly states it finds wallets behaviorally linked to a target wallet via co-buying 3+ tokens within 2 seconds, distinguishing from siblings like madeonsol_alpha_wallet.

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?

Implies usage for linked wallet discovery but lacks explicit when-to-use vs alternatives or when-not-to-use; mentions 'ULTRA only' but no further guidance.

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