Skip to main content
Glama
G-Hensley
by G-Hensley

Get Skills

get_skills

Retrieve skills and proficiency levels, with optional filters for category or minimum level.

Instructions

Get all skills with proficiency levels, optionally filtered by category or level

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category (e.g., 'programming_languages', 'frameworks_and_libraries', 'databases')
min_levelNoMinimum proficiency level

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes

Implementation Reference

  • The handler function for get_skills: fetches skills from GitHub JSON, filters by optional category and min proficiency level, then returns the filtered results as JSON text content.
    async ({ category, min_level }) => {
      const skills = await readJsonFile<SkillsData>("profile/skills.json");
      const levelOrder = skills.skill_levels;
      const minLevelIndex = min_level ? levelOrder.indexOf(min_level) : 0;
      const result: SkillResult[] = [];
    
      for (const [cat, data] of Object.entries(skills.categories)) {
        if (category && cat.toLowerCase() !== category.toLowerCase()) continue;
        for (const skill of data.skills) {
          const skillLevelIndex = levelOrder.indexOf(skill.level);
          if (skillLevelIndex >= minLevelIndex) {
            result.push({ category: cat, name: skill.name, level: skill.level, notes: skill.notes });
          }
        }
      }
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • Input/output schema for get_skills: optional 'category' (string) and 'min_level' (enum from 'none' to 'master') inputs; output is textContentOutputSchema (array of text content).
    {
      title: "Get Skills",
      description: "Get all skills with proficiency levels, optionally filtered by category or level",
      inputSchema: {
        category: z.string().optional().describe("Filter by category (e.g., 'Frontend', 'Backend', 'DevOps')"),
        min_level: z.enum(["none", "novice", "apprentice", "adept", "expert", "master"]).optional().describe("Minimum proficiency level"),
      },
      outputSchema: textContentOutputSchema,
    },
  • api/mcp.ts:68-96 (registration)
    Registration of the 'get_skills' tool via server.registerTool() with title, description, input/output schemas, and handler.
    server.registerTool(
      "get_skills",
      {
        title: "Get Skills",
        description: "Get all skills with proficiency levels, optionally filtered by category or level",
        inputSchema: {
          category: z.string().optional().describe("Filter by category (e.g., 'Frontend', 'Backend', 'DevOps')"),
          min_level: z.enum(["none", "novice", "apprentice", "adept", "expert", "master"]).optional().describe("Minimum proficiency level"),
        },
        outputSchema: textContentOutputSchema,
      },
      async ({ category, min_level }) => {
        const skills = await readJsonFile<SkillsData>("profile/skills.json");
        const levelOrder = skills.skill_levels;
        const minLevelIndex = min_level ? levelOrder.indexOf(min_level) : 0;
        const result: SkillResult[] = [];
    
        for (const [cat, data] of Object.entries(skills.categories)) {
          if (category && cat.toLowerCase() !== category.toLowerCase()) continue;
          for (const skill of data.skills) {
            const skillLevelIndex = levelOrder.indexOf(skill.level);
            if (skillLevelIndex >= minLevelIndex) {
              result.push({ category: cat, name: skill.name, level: skill.level, notes: skill.notes });
            }
          }
        }
        return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
      }
    );
  • Helper function readJsonFile<T> that fetches and parses JSON from GitHub raw content, used by the handler to load skills data.
    async function readJsonFile<T>(relativePath: string): Promise<T> {
      const content = await fetchFromGitHub(relativePath);
      return JSON.parse(content) as T;
    }
  • Type definitions for SkillsData and SkillResult used by the get_skills handler.
    export interface SkillsData {
      skill_levels: string[];
      categories: Record<string, SkillCategory>;
    }
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 indicates a read operation ('Get') but does not mention side effects, authentication needs, rate limits, or data freshness. The existence of an output schema reduces some burden, but behavioral details are sparse.

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?

A single, front-loaded sentence that conveys the core purpose concisely. No unnecessary words, only essential 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 low complexity (2 optional params, output schema present), the description is largely complete. It explains the tool's main action and filtering capability. Minor omission: no mention of pagination or ordering, but this is likely handled by the 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 coverage is 100% with descriptions for both parameters. The description adds context about default behavior ('all skills') and optional filtering, but does not provide significant new meaning beyond the schema. This is baseline adequate.

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 retrieves all skills with proficiency levels, optionally filtered. It uses a specific verb ('Get') and resource ('skills'), making its purpose unambiguous. It distinguishes from sibling 'get_*' tools by focusing on 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?

No explicit guidance on when to use this tool vs alternatives. However, given the sibling tools cover different resources, the use case is implicitly clear. It lacks exclusions or comparisons, so it meets a minimum viable standard.

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/G-Hensley/myself-mcp-server'

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