Skip to main content
Glama

maasy_list_skills

Filter and list Maasy copilot skills by category to find modular knowledge packages for SEO, ads, CRM, content, and other marketing areas.

Instructions

List all maasy copilot skills — modular knowledge packages (SEO, ads, CRM playbooks, etc).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNo
active_onlyNo

Implementation Reference

  • The `toolHandler` function is a generic wrapper that delegates tool invocation to the `callGateway` function. For 'maasy_list_skills', it passes the tool name 'list_skills' to `callGateway`, which sends the request to the Supabase edge function 'mcp-gateway'. The actual handler logic lives server-side in the gateway.
    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,
          };
        }
      };
    }
  • Input schema for maasy_list_skills. Accepts optional 'category' (enum of marketing topic categories) and optional 'active_only' boolean (defaults true).
    {
      category: z
        .enum([
          "copilot",
          "ads",
          "ads_manager",
          "seo_geo",
          "content",
          "email",
          "crm",
          "funnels",
          "landing",
          "video",
          "cultural",
          "general",
        ])
        .optional(),
      active_only: z.boolean().optional().default(true),
    },
  • src/index.ts:87-110 (registration)
    Registration of the 'maasy_list_skills' tool on the MCP server. Name, description, input schema, and handler are all defined here.
    server.tool(
      "maasy_list_skills",
      "List all maasy copilot skills — modular knowledge packages (SEO, ads, CRM playbooks, etc).",
      {
        category: z
          .enum([
            "copilot",
            "ads",
            "ads_manager",
            "seo_geo",
            "content",
            "email",
            "crm",
            "funnels",
            "landing",
            "video",
            "cultural",
            "general",
          ])
          .optional(),
        active_only: z.boolean().optional().default(true),
      },
      toolHandler("list_skills")
    );
  • The `callGateway` helper function that forwards the tool name ('list_skills') and arguments to the Supabase edge function for 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 are provided, so the description solely handles transparency. It states 'list' implying read-only, but does not explicitly confirm non-destructiveness, mention default filter behavior (active_only=true), or describe any side effects or limitations.

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 concise sentence that front-loads the purpose. Every word adds value; no redundant information.

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

Completeness3/5

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

For a simple list tool with no output schema, the description is adequate but incomplete. It does not mention what the return format is, whether pagination exists, or that categories can be filtered. Additional context would improve completeness.

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 0%, so the description must compensate. It briefly mentions examples of skill content but does not explain the category or active_only parameters. The description adds little meaning beyond what the schema already provides.

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 (list) and resource (maasy copilot skills), and explains what skills are (modular knowledge packages). It distinguishes from sibling tools like create_skill or get_skill which address individual skill operations.

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 is implied by the name and description, but no explicit guidance is given on when to use this tool versus alternatives like get_skill or other list tools. No when-to-use or when-not-to-use information is provided.

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