Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_copytrade_delete

DestructiveIdempotent

Delete a copy-trade rule permanently by specifying its subscription id.

Instructions

Delete a copy-trade rule permanently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSubscription id

Implementation Reference

  • src/index.ts:746-754 (registration)
    Tool registration for 'madeonsol_copytrade_delete' on the MCP server via server.tool()
    server.tool(
      "madeonsol_copytrade_delete",
      "Delete a copy-trade rule permanently.",
      { id: z.number().describe("Subscription id") },
      { readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: true },
      async ({ id }) => ({
        content: [{ type: "text" as const, text: await restQuery("DELETE", `/copytrade/subscriptions/${id}`) }],
      })
    );
  • Input schema for the tool: accepts a single 'id' parameter (number, subscription id)
    { id: z.number().describe("Subscription id") },
    { readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: true },
  • Handler function: sends DELETE request to /copytrade/subscriptions/{id} via restQuery helper
      async ({ id }) => ({
        content: [{ type: "text" as const, text: await restQuery("DELETE", `/copytrade/subscriptions/${id}`) }],
      })
    );
  • restQuery helper: generic HTTP request function that handles auth headers, JSON serialization, and error formatting
    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);
    }
Behavior3/5

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

Annotations already indicate destructiveHint=true, and description adds 'permanently' which aligns. No additional behavioral details beyond annotations, but no contradiction.

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?

A single sentence that is direct and without any unnecessary words or information.

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 delete operation with one required parameter and annotations providing behavioral hints, the description is sufficient. No output schema is needed for a delete operation.

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?

The input schema describes the parameter 'id' as 'Subscription id' with 100% coverage. The description adds no extra meaning beyond the schema.

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 'Delete' and the resource 'copy-trade rule', with the qualifier 'permanently'. This distinguishes it from sibling tools like create, update, and list.

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, no prerequisites or conditions for deletion, and no mention of what happens after deletion.

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