Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_coordination_alerts_delete

DestructiveIdempotent

Permanently delete a coordination alert rule using its UUID. Keep your alert system organized by removing obsolete rules.

Instructions

Delete a coordination alert rule permanently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesRule UUID

Implementation Reference

  • Handler for the madeonsol_coordination_alerts_delete tool. Calls restQuery with DELETE method to permanently remove a coordination alert rule by UUID, hitting endpoint /kol/coordination/alerts/{id}.
    server.tool(
      "madeonsol_coordination_alerts_delete",
      "Delete a coordination alert rule permanently.",
      { id: z.string().describe("Rule UUID") },
      { readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: true },
      async ({ id }) => ({
        content: [{ type: "text" as const, text: await restQuery("DELETE", `/kol/coordination/alerts/${encodeURIComponent(id)}`) }],
      })
    );
  • Schema: single required parameter 'id' (string UUID) identifying the coordination alert rule to delete.
    { id: z.string().describe("Rule UUID") },
    { readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: true },
  • src/index.ts:844-852 (registration)
    Tool registered via server.tool() with name 'madeonsol_coordination_alerts_delete' inside the Webhook & Streaming tools section, guarded by hasRestAuth (requires MADEONSOL_API_KEY).
    server.tool(
      "madeonsol_coordination_alerts_delete",
      "Delete a coordination alert rule permanently.",
      { id: z.string().describe("Rule UUID") },
      { readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: true },
      async ({ id }) => ({
        content: [{ type: "text" as const, text: await restQuery("DELETE", `/kol/coordination/alerts/${encodeURIComponent(id)}`) }],
      })
    );
  • Helper function restQuery used by the tool handler to make authenticated REST API calls to the MadeOnSol backend.
    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);
    }
Behavior4/5

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

Annotations already mark the tool as destructive and idempotent. The description adds 'permanently,' reinforcing the irreversible nature. No contradiction with annotations; the extra context is valuable.

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 with no filler words. It is concise and effectively communicates the tool's purpose.

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

Completeness5/5

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

Given the tool's simplicity (one parameter, no output schema, and sufficient annotations), the description provides complete context for an agent to understand the action and its permanence.

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?

With 100% schema coverage and a single parameter (id, described as 'Rule UUID'), the description does not add additional meaning beyond the schema. Baseline score of 3 is appropriate.

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 'Delete a coordination alert rule permanently,' using a specific verb and resource. It is well-distinguished from sibling tools like create, get, list, and update.

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?

The description implies usage for deleting a rule but provides no explicit guidance on when to use this vs. alternatives such as update. Sibling tools suggest related operations, but no when-not or context is given.

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