Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_copytrade_update

Toggle active state and update parameters like wallets, trade size, action type, and delivery mode for a copy-trade rule.

Instructions

Update fields on a copy-trade rule, including is_active toggle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSubscription id
nameNo
source_walletsNo
min_trade_solNo
only_actionNo
sizing_modeNo
sizing_amountNo
delivery_modeNo
webhook_urlNo
is_activeNo

Implementation Reference

  • The handler/executor for the madeonsol_copytrade_update tool. It destructures 'id' from args, collects the remaining patch fields into a body object, and sends a PATCH request to /api/v1/copytrade/subscriptions/{id}.
      async ({ id, ...patch }) => {
        const body: Record<string, unknown> = {};
        for (const [k, v] of Object.entries(patch)) {
          if (v !== undefined) body[k] = v;
        }
        return { content: [{ type: "text" as const, text: await restQuery("PATCH", `/copytrade/subscriptions/${id}`, body) }] };
      }
    );
  • Input schema for madeonsol_copytrade_update using Zod. Defines the parameters: id (number, required), and optional fields name, source_wallets, min_trade_sol, only_action, sizing_mode, sizing_amount, delivery_mode, webhook_url, and is_active.
    {
      id: z.number().describe("Subscription id"),
      name: z.string().nullable().optional(),
      source_wallets: z.array(z.string()).optional(),
      min_trade_sol: z.number().optional(),
      only_action: z.enum(["buy", "sell", "both"]).optional(),
      sizing_mode: z.enum(["fixed", "proportional", "percent_source"]).optional(),
      sizing_amount: z.number().optional(),
      delivery_mode: z.enum(["webhook", "websocket", "both"]).optional(),
      webhook_url: z.string().url().nullable().optional(),
      is_active: z.boolean().optional(),
    },
  • src/index.ts:721-744 (registration)
    Registration of the tool via server.tool() call with the name 'madeonsol_copytrade_update', description, schema object, annotations, and handler function.
    server.tool(
      "madeonsol_copytrade_update",
      "Update fields on a copy-trade rule, including is_active toggle.",
      {
        id: z.number().describe("Subscription id"),
        name: z.string().nullable().optional(),
        source_wallets: z.array(z.string()).optional(),
        min_trade_sol: z.number().optional(),
        only_action: z.enum(["buy", "sell", "both"]).optional(),
        sizing_mode: z.enum(["fixed", "proportional", "percent_source"]).optional(),
        sizing_amount: z.number().optional(),
        delivery_mode: z.enum(["webhook", "websocket", "both"]).optional(),
        webhook_url: z.string().url().nullable().optional(),
        is_active: z.boolean().optional(),
      },
      { readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: true },
      async ({ id, ...patch }) => {
        const body: Record<string, unknown> = {};
        for (const [k, v] of Object.entries(patch)) {
          if (v !== undefined) body[k] = v;
        }
        return { content: [{ type: "text" as const, text: await restQuery("PATCH", `/copytrade/subscriptions/${id}`, body) }] };
      }
    );
  • The restQuery helper function used by the handler to make authenticated REST API calls. It constructs the URL, applies headers (including Bearer auth), sends the request with method and body, and returns the JSON response or an error string.
    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);
    }
Behavior2/5

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

Annotations provide basic info (non-read-only, non-destructive, non-idempotent), but the description adds little beyond stating it updates fields. No disclosure of side effects, permission requirements, or whether updates are partial or full replacements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single concise sentence that conveys the core purpose without fluff. Could be slightly more structured, but effective for its brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (10 parameters, 3 enums, no output schema), the description lacks completeness. It does not explain update behavior (e.g., partial updates, validation rules, response format), which is critical for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 10 parameters with only 10% description coverage (only 'id' described). The description mentions 'fields... including is_active toggle' but fails to explain the meaning or constraints of the other 9 parameters, leaving the agent with minimal guidance.

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 verb 'Update' and the resource 'copy-trade rule', and it distinguishes from sibling tools like create, delete, get, list by focusing on modification. The mention of 'including is_active toggle' adds specificity.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., create or delete). No prerequisites, exclusions, or context about when to update vs recreate a rule.

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