Skip to main content
Glama

maasy_delete_skill

Permanently delete a skill from Maasy AI Marketing Copilot by providing its UUID. Removes all associated knowledge.

Instructions

Permanently delete a skill. Removes the knowledge from maasy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skill_idYesSkill UUID

Implementation Reference

  • src/index.ts:193-198 (registration)
    Registration of the 'maasy_delete_skill' tool on the MCP server via server.tool(), with the name, description, Zod schema (skill_id required string), and the handler delegated to toolHandler('delete_skill').
    server.tool(
      "maasy_delete_skill",
      "Permanently delete a skill. Removes the knowledge from maasy.",
      { skill_id: z.string().describe("Skill UUID") },
      toolHandler("delete_skill")
    );
  • The toolHandler() wrapper that actually executes the tool logic. It calls callGateway(toolName, gatewayArgs) with toolName 'delete_skill' (passed from line 197). It invokes the Supabase edge function mcp-gateway with the tool name and arguments, then returns the JSON result.
    function toolHandler(toolName: string, argsFn?: (args: Record<string, unknown>) => Record<string, unknown>) {
      return async (args: Record<string, unknown>) => {
        try {
          const gatewayArgs = argsFn ? argsFn(args) : args;
          // Auto-inject default project_id if not provided
          if (DEFAULT_PROJECT_ID && !gatewayArgs.project_id) {
            gatewayArgs.project_id = DEFAULT_PROJECT_ID;
          }
          const result = await callGateway(toolName, gatewayArgs);
          return { content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }] };
        } catch (e: unknown) {
          return {
            content: [{ type: "text" as const, text: `Error: ${e instanceof Error ? e.message : String(e)}` }],
            isError: true,
          };
        }
      };
    }
  • The callGateway() function that makes the actual HTTP POST request to the mcp-gateway edge function. It sends the tool name ('delete_skill') and arguments, authenticating with either OAuth token or API key.
    export async function callGateway(tool: string, args: Record<string, unknown> = {}): Promise<unknown> {
      const res = await fetch(gatewayUrl, {
        method: "POST",
        headers: {
          "Content-Type": "application/json",
          [authHeader.name]: authHeader.value,
        },
        body: JSON.stringify({ tool, args }),
      });
    
      const data = await res.json();
    
      if (!res.ok) {
        throw new Error(data.error || `Gateway error (${res.status})`);
      }
    
      return data.result;
    }
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states 'permanently delete' implying irreversibility, but omits details like permission requirements or side effects. It is adequate but not comprehensive.

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 short sentences, perfectly concise with no filler. All information is front-loaded.

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 parameter and no output schema, the description is mostly complete. It could mention that the action is irreversible or that no confirmation is given, but overall it provides the necessary information.

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 already provides 100% coverage for the single parameter (skill_id described as 'Skill UUID'). The description adds no additional meaning beyond the schema, so baseline 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 'Permanently delete a skill' which combines a specific verb (delete) and resource (skill), and it distinguishes from sibling tools like maasy_create_skill and maasy_update_skill.

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, no mention of irreversible consequences or required permissions.

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/Jbelieve/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server