Skip to main content
Glama
osulivan

skill4agent MCP Server

get_skill

Retrieve detailed skill information and complete documentation to verify capabilities before installation or recommendation.

Instructions

Get detailed information about a skill, including the complete SKILL.md content.

Use cases:

  • When you want to learn detailed information about a skill

  • When you need to view the core documentation (SKILL.md) of a skill

  • Before recommending or installing a skill, you need to confirm the detailed information to analyze whether it meets the requirements

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skillIdYesThe skill ID to query. Can be obtained from the results returned by the search_skills tool.

Implementation Reference

  • The main handler function that executes the get_skill tool logic. It takes a skillId parameter, calls the API client to fetch skill details, and returns the result as formatted JSON text. Includes error handling for failed API calls.
    export async function getSkillHandler(
      args: z.infer<typeof getSkillSchema>
    ): Promise<{ content: Array<{ type: 'text'; text: string }> }> {
      const api = getAPIClient();
    
      try {
        const result = await api.getSkill({ skillId: args.skillId });
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        const message = error instanceof Error ? error.message : 'Failed to retrieve';
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                error: message,
                message: 'Failed to get skill. Please check: 1. Parameter format is correct 2. Network connection is normal',
              }, null, 2),
            },
          ],
        };
      }
    }
  • Zod schema definition for the get_skill tool input. Validates that skillId is a required string parameter, with a description explaining it can be obtained from search_skills results.
    export const getSkillSchema = z.object({
      skillId: z.string().describe('The skill ID to query. Can be obtained from the results returned by the search_skills tool.'),
    });
  • src/server.ts:37-46 (registration)
    Registration of the get_skill tool with the MCP server. Registers the tool name, description, input schema, and handler callback function.
    server.registerTool(
      'get_skill',
      {
        description: 'Get detailed information about a skill, including the complete SKILL.md content.\n\nUse cases:\n- When you want to learn detailed information about a skill\n- When you need to view the core documentation (SKILL.md) of a skill\n- Before recommending or installing a skill, you need to confirm the detailed information to analyze whether it meets the requirements',
        inputSchema: getSkillSchema,
      },
      async (args) => {
        return getSkillHandler(args);
      }
    );
  • API client method that makes the actual HTTP GET request to fetch skill details from the endpoint /skills/{skillId}. Handles errors and returns the GetSkillResponse.
    async getSkill(params: GetSkillParams): Promise<GetSkillResponse> {
      try {
        const response = await this.client.get<GetSkillResponse>(
          `/skills/${encodeURIComponent(params.skillId)}`
        );
        return response.data;
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw this.handleError(error);
        }
        throw new Error('Failed to get skill: Unknown error');
      }
    }
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. While it mentions retrieving 'detailed information' and 'SKILL.md content', it doesn't disclose behavioral traits like whether this is a read-only operation, potential rate limits, authentication requirements, error conditions, or what format the information is returned in. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized with a clear purpose statement followed by bullet-pointed use cases. Every sentence earns its place by providing specific guidance, though the third use case could be slightly more concise by combining ideas about 'recommending or installing'.

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 tool's moderate complexity (single parameter, no output schema, no annotations), the description is adequate but incomplete. It covers purpose and usage well, but lacks behavioral transparency about how the tool operates and what it returns. Without annotations or output schema, the description should do more to explain the tool's behavior and response format.

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% (the single parameter 'skillId' is fully described in the schema), so the baseline is 3. The description doesn't add any parameter-specific information beyond what the schema already provides about obtaining skillId from 'search_skills' results.

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 'Get' and resource 'detailed information about a skill', specifically mentioning 'complete SKILL.md content'. It distinguishes from sibling tools like 'search_skills' (which finds skills) and 'install_skill' (which installs them) by focusing on retrieving detailed documentation for a specific skill.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Use cases' section provides clear context for when to use this tool: to learn detailed information, view core documentation, or confirm details before recommending/installing. However, it doesn't explicitly state when NOT to use it (e.g., for finding skills vs. getting details) or name alternatives like 'search_skills' for discovery purposes.

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/osulivan/skill4agent-mcp-server'

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