Skip to main content
Glama

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
NameRequiredDescriptionDefault
skill_idYesSkill 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")
    );
  • 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,
          };
        }
      };
    }
  • 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;
    }
  • Input schema for 'maasy_get_skill': requires a 'skill_id' string (Skill UUID).
    { skill_id: z.string().describe("Skill UUID") },
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It indicates the tool returns 'content and auto-generated quick action pills', which is helpful, but it does not mention that the operation is read-only, any authentication needs, or rate limits. The description is adequate but not rich.

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 sentence that is front-loaded with the action verb and resource. Every word is necessary and there is no extraneous information.

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?

Given that there is no output schema and no annotations, the description provides a reasonable overview of what the tool returns (content and quick action pills). It could be more detailed about response structure or side effects, but for a simple retrieval tool it is fairly complete.

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 has 100% coverage with skill_id described as 'Skill UUID', which is clear. The description adds context about the return value but does not further clarify the parameter meaning beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Get full details of a skill', using a specific verb and resource. It distinguishes from sibling tools like maasy_list_skills by mentioning 'full details', but does not explicitly name alternatives, so a 4 is appropriate.

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 description implies usage when a skill_id is available and full details are needed, but lacks explicit guidance on when to use this versus alternatives like maasy_list_skills or maasy_update_skill. No exclusions or prerequisites are mentioned.

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