Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_delete_webhook

DestructiveIdempotent

Permanently delete a webhook and its delivery history by providing the webhook ID.

Instructions

Delete a webhook by ID. Permanently removes the webhook and its delivery history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWebhook ID to delete

Implementation Reference

  • The handler for the madeonsol_delete_webhook tool. It accepts an 'id' parameter (number), makes a DELETE request to /api/v1/webhooks/{id} via the restQuery helper, and returns the response text.
    server.tool(
      "madeonsol_delete_webhook",
      "Delete a webhook by ID. Permanently removes the webhook and its delivery history.",
      {
        id: z.number().describe("Webhook ID to delete"),
      },
      { readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: true },
      async ({ id }) => ({
        content: [{ type: "text" as const, text: await restQuery("DELETE", `/webhooks/${id}`) }],
      })
  • Input schema for madeonsol_delete_webhook: requires a single numeric 'id' parameter representing the webhook ID to delete.
    {
      id: z.number().describe("Webhook ID to delete"),
    },
  • src/index.ts:500-510 (registration)
    Registration of the madeonsol_delete_webhook tool on the McpServer instance via server.tool(). Conditionally registered only when authMode is 'madeonsol' (i.e., MADEONSOL_API_KEY is set).
    server.tool(
      "madeonsol_delete_webhook",
      "Delete a webhook by ID. Permanently removes the webhook and its delivery history.",
      {
        id: z.number().describe("Webhook ID to delete"),
      },
      { readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: true },
      async ({ id }) => ({
        content: [{ type: "text" as const, text: await restQuery("DELETE", `/webhooks/${id}`) }],
      })
    );
  • Helper function restQuery used by the delete webhook handler. It makes an authenticated fetch to the MadeOnSol API v1 endpoint with the given HTTP method, path, and optional body. The handler calls restQuery('DELETE', '/webhooks/${id}').
    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 destructiveHint=true, but the description adds the behavioral detail that delivery history is also permanently removed. No contradiction with annotations.

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 action, and every sentence adds value. No wasted 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?

Given the simple 1-parameter tool with annotations, the description adequately covers purpose and permanent nature. No output schema, but return value is implicit 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?

Schema description coverage is 100% and the description only adds 'by ID' which is redundant with the required 'id' parameter. No new 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 'Delete a webhook by ID' with the verb 'Delete' and resource 'webhook'. It distinguishes itself from sibling webhook tools like create, list, and test by specifying the delete action.

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 implies when to use this tool (to delete a webhook) and signals permanence, though it doesn't explicitly exclude alternative actions. The sibling list confirms this is the only delete tool, making usage clear.

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