Skip to main content
Glama
lyupro
by lyupro

Get skill

skills__get

Retrieve the complete body and metadata of a named skill for use in toolchains or automation.

Instructions

Retrieve the full content (body + metadata) of a named skill.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Implementation Reference

  • The main handler function for the skills__get tool. Looks up a skill by name in the registry, returning cached content or parsing from disk.
    export async function handleGet(deps: ServerDeps, args: { name: string }): Promise<SkillContent> {
      await ensureRegistryFresh(deps);
    
      if (!deps.registry.has(args.name)) {
        throw new Error(`Skill not found: ${args.name}`);
      }
    
      const cached = deps.contentCache.get(args.name);
      if (cached !== undefined) return cached;
    
      // Cache miss — re-parse from disk using the metadata's location.
      const meta = deps.registry.get(args.name)!;
      const content = await deps.parser.parseFile(meta.sourcePath, meta.folder);
      deps.contentCache.set(args.name, content);
      return content;
    }
  • Input schema for skills__get, defines a 'name' string parameter.
    export const getInputSchema = {
      name: z.string(),
    } as const;
  • src/tools/index.ts:2-2 (registration)
    Re-exports getInputSchema and handleGet from the get.ts module.
    export { getInputSchema, handleGet } from './get.js';
Behavior3/5

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

The description indicates a read operation (retrieve) but lacks explicit statements about safety, permissions, or side effects. Since no annotations are provided, the description carries the burden; however, for a simple retrieval, the minimal description is adequate but not thorough.

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 a single, clear sentence that front-loads the key information. It is efficient and easy to parse, though slightly more detail could be added without harming conciseness.

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 simplicity (one parameter, no output schema), the description is minimally complete. It explains the return value (body + metadata) but omits context like how to obtain skill names or any relationship to sibling tools, which limits completeness for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no descriptions, and the tool description adds no meaning beyond stating that the parameter 'name' refers to a skill's name. With 0% schema coverage, the description should compensate by explaining what constitutes a valid name (e.g., format, where to obtain it), but it does not.

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 states the verb 'Retrieve' and specifies the resource as 'full content (body + metadata) of a named skill.' This clearly distinguishes it from sibling tools like skills__list (which likely lists names only) and skills__configure/invoke/reload (which perform other actions).

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not explain that skills__get is for full details while skills__list is for summaries, nor does it mention any prerequisites like needing the skill name from prior listing.

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/lyupro/skillforge-mcp'

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