Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_wallet_tracker_remove

DestructiveIdempotent

Remove a Solana wallet from your monitored watchlist to stop tracking its trades and analytics.

Instructions

Remove a wallet from your watchlist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_addressYesSolana wallet address to remove from watchlist

Implementation Reference

  • src/index.ts:386-396 (registration)
    Registration of the 'madeonsol_wallet_tracker_remove' tool via server.tool() with its schema and handler.
    server.tool(
      "madeonsol_wallet_tracker_remove",
      "Remove a wallet from your watchlist.",
      {
        wallet_address: z.string().describe("Solana wallet address to remove from watchlist"),
      },
      { readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: true },
      async ({ wallet_address }) => ({
        content: [{ type: "text" as const, text: await walletTrackerRequest("DELETE", `/wallet-tracker/watchlist/${encodeURIComponent(wallet_address)}`) }],
      })
    );
  • Handler function: sends a DELETE request to the wallet-tracker/watchlist/{wallet_address} endpoint to remove a wallet from the watchlist.
    async ({ wallet_address }) => ({
      content: [{ type: "text" as const, text: await walletTrackerRequest("DELETE", `/wallet-tracker/watchlist/${encodeURIComponent(wallet_address)}`) }],
    })
  • Input schema: requires a single string parameter 'wallet_address' (base58 Solana wallet address).
    {
      wallet_address: z.string().describe("Solana wallet address to remove from watchlist"),
    },
  • Helper function walletTrackerRequest used by the remove handler to make the DELETE API call with JSON headers and auth.
    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);
    }
Behavior3/5

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

Annotations indicate destructive and idempotent behavior. The description matches but adds no additional context (e.g., what happens if wallet not in watchlist).

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 a single sentence that directly states the tool's function with no unnecessary 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?

For a simple one-parameter tool with no output schema, the description is sufficient to convey the core action. It covers the essential need but could mention response 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?

Input schema covers 100% of parameters with a clear description. The tool description does not add extra meaning beyond what the schema already provides.

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 the action (remove) and the resource (wallet from watchlist). This distinguishes it from sibling tools like 'add' or 'summary'.

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. While the purpose is clear, there is no mention of prerequisites or situations where removal might be inappropriate.

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