Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_wallet_tracker_trades

Read-onlyIdempotent

Retrieve historical swap and transfer events from tracked Solana wallets. Filter by wallet, action type, event type, and paginate results.

Instructions

Historical swap and transfer events for all your watched wallets. BASIC: truncated wallets, no tx_signature.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletNoFilter to a specific wallet address
actionNoFilter by action type
event_typeNoFilter by event type: swap (token trade) or transfer (SOL moved)
limitNoMax results (1–200)
beforeNoPagination cursor: block_time of the last event from previous page

Implementation Reference

  • The tool handler for 'madeonsol_wallet_tracker_trades'. It registers via server.tool with a Zod schema for parameters (wallet, action, event_type, limit, before) and implements the async handler that constructs a URL to /api/v1/wallet-tracker/trades, attaches query params, fetches with API key auth, and returns JSON results. Gated behind authMode === 'madeonsol'.
    server.tool(
      "madeonsol_wallet_tracker_trades",
      "Historical swap and transfer events for all your watched wallets. BASIC: truncated wallets, no tx_signature.",
      {
        wallet: z.string().optional().describe("Filter to a specific wallet address"),
        action: z.enum(["buy", "sell", "transfer_in", "transfer_out"]).optional().describe("Filter by action type"),
        event_type: z.enum(["swap", "transfer"]).optional().describe("Filter by event type: swap (token trade) or transfer (SOL moved)"),
        limit: z.number().min(1).max(200).default(50).describe("Max results (1–200)"),
        before: z.number().optional().describe("Pagination cursor: block_time of the last event from previous page"),
      },
      { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      async ({ wallet, action, event_type, limit, before }) => {
        const params: Record<string, string | number> = { limit };
        if (wallet) params.wallet = wallet;
        if (action) params.action = action;
        if (event_type) params.event_type = event_type;
        if (before !== undefined) params.before = before;
        const url = new URL(`${BASE_URL}/api/v1/wallet-tracker/trades`);
        for (const [k, v] of Object.entries(params)) url.searchParams.set(k, String(v));
        const res = await fetch(url.toString(), { headers: { "Content-Type": "application/json", ...apiKeyHeaders() } });
        const text = res.ok ? JSON.stringify(await res.json(), null, 2) : `Error ${res.status}: ${await res.text().catch(() => "")}`;
        return { content: [{ type: "text" as const, text }] };
      }
    );
  • Input schema for madeonsol_wallet_tracker_trades using Zod: optional wallet (string), optional action (buy/sell/transfer_in/transfer_out), optional event_type (swap/transfer), limit (1-200, default 50), optional before (number pagination cursor).
    {
      wallet: z.string().optional().describe("Filter to a specific wallet address"),
      action: z.enum(["buy", "sell", "transfer_in", "transfer_out"]).optional().describe("Filter by action type"),
      event_type: z.enum(["swap", "transfer"]).optional().describe("Filter by event type: swap (token trade) or transfer (SOL moved)"),
      limit: z.number().min(1).max(200).default(50).describe("Max results (1–200)"),
      before: z.number().optional().describe("Pagination cursor: block_time of the last event from previous page"),
    },
  • src/index.ts:398-421 (registration)
    Registration of the 'madeonsol_wallet_tracker_trades' tool via server.tool() within the Wallet Tracker tools section (line 343). Only registered if hasRestAuth (authMode === 'madeonsol') is true.
    server.tool(
      "madeonsol_wallet_tracker_trades",
      "Historical swap and transfer events for all your watched wallets. BASIC: truncated wallets, no tx_signature.",
      {
        wallet: z.string().optional().describe("Filter to a specific wallet address"),
        action: z.enum(["buy", "sell", "transfer_in", "transfer_out"]).optional().describe("Filter by action type"),
        event_type: z.enum(["swap", "transfer"]).optional().describe("Filter by event type: swap (token trade) or transfer (SOL moved)"),
        limit: z.number().min(1).max(200).default(50).describe("Max results (1–200)"),
        before: z.number().optional().describe("Pagination cursor: block_time of the last event from previous page"),
      },
      { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      async ({ wallet, action, event_type, limit, before }) => {
        const params: Record<string, string | number> = { limit };
        if (wallet) params.wallet = wallet;
        if (action) params.action = action;
        if (event_type) params.event_type = event_type;
        if (before !== undefined) params.before = before;
        const url = new URL(`${BASE_URL}/api/v1/wallet-tracker/trades`);
        for (const [k, v] of Object.entries(params)) url.searchParams.set(k, String(v));
        const res = await fetch(url.toString(), { headers: { "Content-Type": "application/json", ...apiKeyHeaders() } });
        const text = res.ok ? JSON.stringify(await res.json(), null, 2) : `Error ${res.status}: ${await res.text().catch(() => "")}`;
        return { content: [{ type: "text" as const, text }] };
      }
    );
  • The walletTrackerRequest helper function used by wallet tracker tools. It constructs an HTTP request to /api/v1/{path} with JSON content-type and Bearer auth headers.
    async function walletTrackerRequest(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 declare readOnlyHint=true and idempotentHint=true, and the description adds useful context: 'truncated wallets, no tx_signature'. This addresses output limitations beyond the annotations, enhancing transparency.

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 the core purpose. Every word serves a purpose, with no 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 the lack of output schema and 5 well-described parameters, the description covers the essential behavior and limitation. Pagination is implied by the 'before' parameter but not detailed; still adequate.

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 parameter descriptions, so the baseline is 3. The description does not add any new meaning or guidance for parameters; it focuses on tool purpose and output limitation.

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 explicitly states the tool provides 'historical swap and transfer events' for watched wallets, distinguishing it from sibling tools like wallet_tracker_summary. The 'BASIC' qualifier adds specificity about output limitations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly indicates when to use the tool for historical trade events, but does not explicitly mention when not to use it or provide alternatives, though the sibling set suggests no direct overlap.

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