Skip to main content
Glama

skills_get_details

Retrieve documentation and file structure for installed skills to understand their functionality and usage instructions.

Instructions

Read the instruction manual (SKILL.md) and file structure of a locally installed skill. Use this to learn how to use a skill after installing it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the installed skill

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'skills_get_details' tool, including registration via @mcp.tool() decorator and Pydantic schema via Field. Formats output from local.get_details.
    @mcp.tool()
    def skills_get_details(
        name: str = Field(description="Name of the installed skill")
    ) -> str:
        """
        Read the instruction manual (SKILL.md) and file structure of a locally installed skill.
        Use this to learn how to use a skill after installing it.
        """
        try:
            details = local.get_details(name)
            return f"""# Skill: {name}
    Path: {details['path']}
    
    ## File Structure
    ```
    {details['tree']}
    ```
    
    ## Instructions
    {details['instruction']}
    """
        except Exception as e:
            return f"Error getting details: {str(e)}"
  • Core helper function that implements the logic to retrieve skill details: path, file tree, and SKILL.md content.
    def get_details(name: str) -> Dict[str, str]:
        target_dir = config.root_dir / name
        if not target_dir.exists():
            raise FileNotFoundError(f"Skill '{name}' is not installed locally.")
    
        skill_md = target_dir / "SKILL.md"
        if not skill_md.exists():
            raise FileNotFoundError(f"Corrupted skill '{name}': SKILL.md missing.")
    
        return {
            "path": str(target_dir),
            "tree": generate_tree(target_dir),
            "instruction": skill_md.read_text(encoding="utf-8")
        }
  • Supporting utility to generate a filtered visual file tree of the skill directory, used by get_details.
    def generate_tree(root_path: Path) -> str:
        """Generates a visual file tree string, filtering out noise."""
        output = []
    
        # Walk the directory
        for dirpath, dirnames, filenames in os.walk(root_path):
            # 1. In-place filtering of directories to prevent recursion into ignored dirs
            dirnames[:] = [d for d in dirnames if d not in IGNORED_DIRS and not d.startswith(".")]
    
            rel_path = Path(dirpath).relative_to(root_path)
    
            if rel_path == Path("."):
                level = 0
            else:
                level = len(rel_path.parts)
                indent = "  " * (level - 1)
                output.append(f"{indent}- {rel_path.name}/")
    
            sub_indent = "  " * level
            for f in sorted(filenames):
                if f in IGNORED_FILES or f.startswith("."):
                    continue
                if any(f.endswith(ext) for ext in IGNORED_EXTENSIONS):
                    continue
    
                output.append(f"{sub_indent}- {f}")
    
        return "\n".join(output)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes a read-only operation ('Read'), which implies non-destructive behavior, but doesn't mention potential side effects, authentication needs, rate limits, or error conditions. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 extremely concise and well-structured in two sentences. The first sentence states the core functionality, and the second provides usage context. Every word earns its place with zero waste, making it easy to parse and understand quickly.

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 the tool's moderate complexity (single parameter, read operation) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers the purpose and basic usage, though it could benefit from more behavioral details given the lack of annotations. The output schema reduces the need to explain return values in the description.

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% description coverage, with the single parameter 'name' documented as 'Name of the installed skill'. The description doesn't add any parameter-specific information beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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: reading the instruction manual (SKILL.md) and file structure of a locally installed skill. It uses specific verbs ('Read') and resources ('instruction manual', 'file structure'), but doesn't explicitly differentiate from sibling tools like skills_list or skills_search, which might also provide skill information.

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?

The description provides implied usage guidance: 'Use this to learn how to use a skill after installing it.' This suggests when to use the tool (post-installation learning), but doesn't explicitly state when not to use it or name alternatives like skills_search for finding skills before installation. The guidance is helpful but not comprehensive.

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/leezhuuuuu/skills-mcp'

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