Skip to main content
Glama
JeremyLakeyJr

Friday MCP Server

get_skill

Retrieve the complete installed content and metadata for a specific skill by providing its skill ID.

Instructions

Get the full installed content and metadata for a skill.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skill_idYes

Implementation Reference

  • The MCP tool handler function for 'get_skill'. It is decorated with @mcp.tool() and delegates to skill_store.get_skill().
    @mcp.tool()
    def get_skill(skill_id: str) -> dict:
        """Get the full installed content and metadata for a skill."""
        return skill_store.get_skill(skill_id)
  • The SkillStore.get_skill() method that loads the skill from the registry and reads its content from disk. Returns the record with full content.
    def get_skill(self, skill_id: str) -> dict[str, Any]:
        registry = self._load_registry()
        record = registry.get(skill_id)
        if record is None:
            raise SkillError(f"Unknown skill '{skill_id}'.")
    
        content = Path(record["path"]).read_text(encoding="utf-8")
        return {
            **record,
            "content": content,
        }
  • The register_all_tools function that calls skills.register(mcp, skill_store=skill_store) to register the get_skill tool.
    def register_all_tools(mcp, *, config, skill_store) -> None:
        system.register(mcp, config=config)
        utils.register(mcp)
        web.register(mcp, config=config)
        workspace.register(mcp, config=config)
        skills.register(mcp, skill_store=skill_store)
  • The server bootstrap where register_all_tools is invoked with the MCP instance and skill_store, completing the tool registration chain.
        register_all_tools(mcp, config=config, skill_store=skill_store)
        register_all_prompts(mcp)
        register_all_resources(mcp, config=config, skill_store=skill_store)
        return mcp
    
    
    mcp = build_server()
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It only states 'get,' implying read-only, but does not explicitly confirm no side effects, nor mention authorization needs or performance considerations. Minimal behavioral context beyond the name.

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?

One concise sentence, front-loaded with key action and object. No redundancy. However, could be expanded slightly to cover parameter semantics without harming brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and simple one-param input, the description omits return type, side effects, and error conditions. For a retrieval tool, the agent needs to know what 'full content' means and what format the response takes. Incomplete for reliable invocation.

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?

Schema description coverage is 0%; the description adds no meaning to the 'skill_id' parameter. The schema provides type and required status, but the description could clarify what a skill ID looks like or how to obtain one, which it does not.

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 retrieves 'full installed content and metadata for a skill,' which is a specific verb+resource. It implies retrieval, distinguishing it from list_skills (likely just listing names) and other mutation tools, but does not explicitly differentiate from siblings.

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 on when to use this tool vs alternatives like list_skills or explain_skill_error. No context about prerequisites (e.g., skill must exist), making it unclear for an agent when to select this over siblings.

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

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