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;
    }
Behavior2/5

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

No annotations exist, so the description must cover behavioral traits. It only mentions regeneration of quick action pills on content change, lacking other important aspects like idempotency, partial update behavior, permissions, or rate limits.

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 consists of two concise sentences, front-loaded with the verb and resource, and no redundant information.

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?

Given no output schema, no annotations, and 8 parameters with low schema coverage, the description fails to provide sufficient context. Missing: return value, constraints, usage patterns, and behavior when multiple fields are updated.

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 described). The description lists updatable fields (content, category, priority, active status) but does not explain other parameters (name, description, max_tokens) or the meaning of the category enum. It adds marginal value but does not compensate for low coverage.

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 tool updates specific fields of a skill (content, category, priority, active status) and mentions a side effect (regenerating quick action pills). This distinguishes it from sibling tools like maasy_create_skill and maasy_delete_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 is provided on when to use this tool versus alternatives (e.g., when to update vs. create a new skill). It does not mention any prerequisites or exclusions.

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