Skip to main content
Glama

get_skill

Retrieve detailed instructions and executable steps for a specific skill from the Hivemind MCP knowledge base to implement debugging solutions.

Instructions

Get detailed information about a specific skill including full instructions and executable steps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skill_idYesThe ID of the skill to retrieve

Implementation Reference

  • Input schema definition for the 'get_skill' tool, specifying skill_id as required number input.
    {
      name: "get_skill",
      description:
        "Get detailed information about a specific skill including full instructions and executable steps.",
      inputSchema: {
        type: "object",
        properties: {
          skill_id: {
            type: "number",
            description: "The ID of the skill to retrieve",
          },
        },
        required: ["skill_id"],
      },
    },
  • src/index.ts:394-399 (registration)
    MCP server registration and dispatch handler for 'get_skill' tool call, invokes getSkill function from api.ts.
    case "get_skill": {
      const result = await getSkill(args?.skill_id as number);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • Core handler implementation: Calls Supabase edge function /skill endpoint with skill_id to retrieve skill details from database.
    export async function getSkill(skillId: number): Promise<SkillDetailResult> {
      const response = await fetch(`${API_BASE}/skill`, {
        method: "POST",
        headers: {
          "Content-Type": "application/json",
        },
        body: JSON.stringify({ skill_id: skillId }),
      });
    
      if (!response.ok) {
        throw new Error(`Get skill failed: ${response.statusText}`);
      }
    
      return response.json();
    }
  • Backend Supabase edge function handler: Queries 'knowledge_entries' table for skill by id and type='skill', returns full record.
    async function handleGetSkill(supabase: any, body: any, corsHeaders: any) {
      const { skill_id } = body;
    
      if (!skill_id) {
        return new Response(JSON.stringify({ error: 'skill_id required' }), {
          status: 400,
          headers: { ...corsHeaders, 'Content-Type': 'application/json' }
        });
      }
    
      const { data, error } = await supabase
        .from('knowledge_entries')
        .select('*')
        .eq('id', skill_id)
        .eq('type', 'skill')
        .single();
    
      if (error || !data) {
        return new Response(JSON.stringify({ error: 'Skill not found' }), {
          status: 404,
          headers: { ...corsHeaders, 'Content-Type': 'application/json' }
        });
      }
    
      return new Response(JSON.stringify({
        ...data,
        _ctx: "Executing skill from global hivemind. Collective knowledge at your fingertips."
      }), {
        headers: { ...corsHeaders, 'Content-Type': 'application/json' }
      });
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but lacks details on permissions, rate limits, error handling, or response format. This is a significant gap for a tool with no structured annotations.

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, efficient sentence that front-loads the core action ('Get detailed information') and specifies the resource and details without any wasted words. Every part of the sentence contributes directly to understanding the tool's function.

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 low complexity (one parameter, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose but lacks behavioral context and usage guidelines, which are needed for full agent understanding in the absence of annotations.

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, fully describing the single parameter 'skill_id' as 'The ID of the skill to retrieve'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline score when schema coverage is high.

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 the tool's purpose with specific verbs ('Get detailed information') and resource ('about a specific skill'), including what information is retrieved ('full instructions and executable steps'). However, it doesn't explicitly differentiate from sibling tools like 'search_skills' or 'count_skills', which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'search_skills' or 'list_my_hives'. It mentions retrieving a specific skill but doesn't clarify prerequisites, such as needing a skill_id, or exclusions, like when to use other tools for broader queries.

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/Kevthetech143/hivemind-mcp'

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