Skip to main content
Glama

maasy_update_skill

Update a skill's content, category, priority, or active status. Automatically regenerates quick action pills when content changes.

Instructions

Update a skill's content, category, priority, or active status. Regenerates quick action pills if content changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skill_idYesSkill UUID
nameNo
descriptionNo
categoryNo
contentNo
priorityNo
max_tokensNo
is_activeNo

Implementation Reference

  • src/index.ts:162-191 (registration)
    Registration of the 'maasy_update_skill' tool on the MCP server, defining its description and input schema (skill_id required; name, description, category, content, priority, max_tokens, is_active optional).
    server.tool(
      "maasy_update_skill",
      "Update a skill's content, category, priority, or active status. Regenerates quick action pills if content changes.",
      {
        skill_id: z.string().describe("Skill UUID"),
        name: z.string().optional(),
        description: z.string().optional(),
        category: z
          .enum([
            "copilot",
            "ads",
            "ads_manager",
            "seo_geo",
            "content",
            "email",
            "crm",
            "funnels",
            "landing",
            "video",
            "cultural",
            "general",
          ])
          .optional(),
        content: z.string().optional(),
        priority: z.number().min(0).max(100).optional(),
        max_tokens: z.number().min(100).max(2000).optional(),
        is_active: z.boolean().optional(),
      },
      toolHandler("update_skill")
    );
  • Generic toolHandler function that wraps every tool call. For 'maasy_update_skill', it calls callGateway('update_skill', ...) which sends the tool name and args to the remote mcp-gateway edge function.
    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,
          };
        }
      };
    }
  • callGateway — the actual network call that sends the tool name ('update_skill') and its arguments to the Supabase edge function 'mcp-gateway' for remote execution.
    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;
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses a specific side effect: 'Regenerates quick action pills if content changes.' However, it does not mention return values, error behavior, or whether updates are partial or full, leaving notable gaps.

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 two concise sentences. The first sentence states the action and fields, and the second adds the key side effect. No wasted words; information is front-loaded.

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?

With 8 parameters, no output schema, and no annotations, the description omits essential context such as what the tool returns, how partial updates are handled, and any error conditions. The side-effect mention is helpful but insufficient for a tool with this complexity.

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 description coverage is only 13% (only skill_id has a description). The description names four fields (content, category, priority, active status) but omits name, max_tokens, and description, and does not clarify semantics like priority range or whether null values unset fields. It adds little 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 'update' and the resource 'skill', and specifies the modifiable fields: content, category, priority, or active status. This distinguishes it from sibling create/delete tools, making the purpose unambiguous.

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?

Usage context is implied by the word 'update' and the resource 'skill', but the description does not explicitly say when to prefer this over create/delete or other sibling tools. It provides clear context (modifying existing skills) but lacks explicit exclusions or alternative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.