Skip to main content
Glama

skills_search

Search a global registry of community-contributed AI agent skills to extend capabilities for specialized tasks and workflows.

Instructions

Search the extended Agent Skills Registry. Use this tool WHENEVER the user asks to 'find skills', 'search skills', or needs capabilities that you do not natively possess (e.g. specialized file handling, complex workflows). This registry contains community-contributed skills that extend your native capabilities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch keywords
pageNoPage number
limitNoItems per page

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main execution logic for the 'skills_search' MCP tool. It creates a RegistryClient, performs the search, formats the results into a readable list, and handles errors.
    def skills_search(
        query: str = Field(description="Search keywords"),
        page: int = Field(default=1, description="Page number"),
        limit: int = Field(default=10, description="Items per page")
    ) -> str:
        """
        Search the extended Agent Skills Registry. Use this tool WHENEVER the user asks to 'find skills', 'search skills', or needs capabilities that you do not natively possess (e.g. specialized file handling, complex workflows). This registry contains community-contributed skills that extend your native capabilities.
        """
        client = api.RegistryClient()
        try:
            results = client.search(query, page, limit)
    
            # Format for LLM
            # 优先取 "skills",为了兼容性也 fallback 到 "items"
            items = results.get("skills", results.get("items", []))
            if not items:
                return "No skills found matching your query."
    
            output = [f"Found {len(items)} skills (Page {page}):"]
            for item in items:
                output.append(f"- {item['name']} (v{item.get('version', '?')}): {item['description']}")
    
            return "\n".join(output)
        except Exception as e:
            return f"Error searching skills: {str(e)}"
  • Pydantic input schema definitions for the skills_search tool parameters using Field for descriptions and defaults.
    query: str = Field(description="Search keywords"),
    page: int = Field(default=1, description="Page number"),
    limit: int = Field(default=10, description="Items per page")
  • The @mcp.tool() decorator registers the skills_search function as an available tool in the FastMCP server.
    @mcp.tool()
  • Supporting helper method in RegistryClient that executes the HTTP GET request to the skills registry search endpoint and handles responses/errors.
    def search(self, query: str = "", page: int = 1, limit: int = 20) -> Dict[str, Any]:
        """Search skills from the registry."""
        params = {"q": query, "page": page, "limit": limit}
        try:
            resp = httpx.get(f"{self.base_url}/skills", params=params, headers=self.headers, timeout=10.0)
            resp.raise_for_status()
            return resp.json()
        except httpx.HTTPStatusError as e:
            if e.response.status_code == 401:
                raise PermissionError("Registry authentication failed. Check SKILLS_API_KEY.")
            raise RuntimeError(f"Registry error: {e.response.text}")
        except httpx.RequestError as e:
            raise RuntimeError(f"Network error connecting to registry: {str(e)}")
Behavior3/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. It mentions the registry contains 'community-contributed skills' and extends capabilities, but lacks details on authentication needs, rate limits, or response behavior. It doesn't contradict annotations, but could provide more operational context.

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 front-loaded with purpose and usage guidelines in two sentences. It's efficient but could be slightly more concise by combining some phrasing. Every sentence adds value, with no wasted words.

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 has an output schema, the description doesn't need to explain return values. It covers purpose and usage well, but as a search tool with no annotations, it could benefit from more behavioral context like result format or error handling. Still, it's largely complete for its complexity.

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 description coverage is 100%, so the schema fully documents parameters (query, page, limit). The description doesn't add meaning beyond the schema, such as query syntax examples or pagination behavior. Baseline 3 is appropriate when schema handles parameter documentation.

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 searches an 'extended Agent Skills Registry' and specifies it's for 'community-contributed skills that extend your native capabilities.' It distinguishes from siblings by focusing on search functionality rather than getting details, installing, or listing skills.

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

Usage Guidelines5/5

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

The description provides explicit usage triggers: 'WHENEVER the user asks to find skills, search skills, or needs capabilities you do not natively possess.' It gives concrete examples like 'specialized file handling, complex workflows,' offering clear guidance on when to use this tool versus alternatives.

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