Skip to main content
Glama
amazingashis

skills-mcp-server

by amazingashis

get_skill

Retrieve the full SKILL.md file for a given skill ID. Get detailed instructions and context for a specific skill.

Instructions

Load the full SKILL.md contents for a skill id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skill_idYesSkill id as returned by list_skills

Implementation Reference

  • The tool handler for 'get_skill'. It calls registry.getSkillMarkdown(skill_id) and returns the full SKILL.md text for a given skill id.
    server.registerTool(
      "get_skill",
      {
        description: "Load the full SKILL.md contents for a skill id.",
        inputSchema: {
          skill_id: z.string().describe("Skill id as returned by list_skills"),
        },
      },
      async ({ skill_id }) => {
        tracker?.recordToolCall("get_skill", { skill_id });
        const text = await registry.getSkillMarkdown(skill_id);
        if (!text) {
          return {
            content: [{ type: "text", text: `Skill not found: ${skill_id}` }],
            isError: true,
          };
        }
        return {
          content: [{ type: "text", text }],
        };
      },
    );
  • Input schema for the 'get_skill' tool, expecting a 'skill_id' string parameter.
    inputSchema: {
      skill_id: z.string().describe("Skill id as returned by list_skills"),
    },
  • Registration of 'get_skill' tool on the MCP server via server.registerTool().
    server.registerTool(
      "get_skill",
      {
        description: "Load the full SKILL.md contents for a skill id.",
        inputSchema: {
          skill_id: z.string().describe("Skill id as returned by list_skills"),
        },
      },
      async ({ skill_id }) => {
        tracker?.recordToolCall("get_skill", { skill_id });
        const text = await registry.getSkillMarkdown(skill_id);
        if (!text) {
          return {
            content: [{ type: "text", text: `Skill not found: ${skill_id}` }],
            isError: true,
          };
        }
        return {
          content: [{ type: "text", text }],
        };
      },
    );
  • The getSkillMarkdown() method on SkillsRegistry that loads the full SKILL.md file for a given skill ID.
    async getSkillMarkdown(skillId: string): Promise<string | null> {
      const list = await this.listSkills();
      const hit = list.find((s) => s.id === skillId);
      if (!hit) return null;
      try {
        return await fs.readFile(hit.filePath, "utf8");
      } catch {
        return null;
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'Load the full SKILL.md contents' with no details on side effects, authentication needs, or what 'full contents' entails (e.g., format, size 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?

Single sentence, front-loaded, no wasted words. Perfectly concise for the information it conveys.

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?

Given the low complexity (1 param, no nested objects), the description is adequate but lacks guidance on return format or constraints, which would be helpful since there is no output schema.

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?

Schema description coverage is 100% and the description adds no extra meaning beyond the schema's existing explanation.

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 action ('Load the full SKILL.md contents') and the resource ('for a skill id'), distinguishing it from sibling tools like list_skills and search_skills.

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 needing the full contents of a specific skill, but no explicit guidance on when to use versus alternatives or when not to use.

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/amazingashis/mcp-deployment'

If you have feedback or need assistance with the MCP directory API, please join our Discord server