Maasy MCP

maasy_get_skill

Retrieve comprehensive details of a skill, including its content and auto-generated quick action pills, by providing the skill UUID.

Instructions

Get full details of a skill including content and auto-generated quick action pills.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`skill_id`	Yes	Skill UUID

Implementation Reference

src/index.ts:112-117 (registration)

Registration of the 'maasy_get_skill' tool on the MCP server with schema (skill_id) and handler (toolHandler('get_skill')).

server.tool(
  "maasy_get_skill",
  "Get full details of a skill including content and auto-generated quick action pills.",
  { skill_id: z.string().describe("Skill UUID") },
  toolHandler("get_skill")
);

src/index.ts:26-43 (handler)

The toolHandler function wraps the actual callGateway call. For 'maasy_get_skill', it calls callGateway('get_skill', { skill_id, ... }) and returns the result as JSON text.

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,
      };
    }
  };
}

src/supabase.ts:42-59 (helper)

The callGateway function that sends the tool name ('get_skill') and arguments to the Supabase edge function gateway. This is the actual execution layer.

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;
}

src/index.ts:115-115 (schema)
Input schema for 'maasy_get_skill': requires a 'skill_id' string (Skill UUID).
```
{ skill_id: z.string().describe("Skill UUID") },
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.1Apr 29, 2026

TDQS

A4/5.0

Behavior4/5

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

The description discloses the key behavioral aspect of the return value: it includes content and auto-generated quick action pills. As a 'get' operation, the read-only nature is self-evident, and unlike a mutation, there are no additional side effects to disclose. This adds practical context beyond the minimal schema.

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 action and key details. Every word earns its place, with no redundancy or filler.

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 read operation with one parameter and no output schema, the description sufficiently explains what the tool does and what the response will include (content, pills). It could mention return format or error handling, but these are minor gaps for a basic get tool.

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 schema already documents skill_id as 'Skill UUID' with 100% coverage. The description does not elaborate on the parameter beyond implicitly referring to the skill, so it provides no additional semantic value.

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's function with a specific verb ('Get') and resource ('skill'), and differentiates it from siblings like maasy_list_skills by specifying 'full details' including 'content and auto-generated quick action pills'.

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?

The usage is implied: this is the tool to retrieve full skill details, as opposed to listing skills or executing actions. However, there is no explicit guidance on when to prefer this over alternatives or any exclusions.

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