Skip to main content
Glama
amazingashis

skills-mcp-server

by amazingashis

search_skills

Find skills by searching their id, title, or description with a case-insensitive substring query.

Instructions

Filter skills by free-text query over id, title, and description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesCase-insensitive substring match

Implementation Reference

  • Registers the "search_skills" tool on the MCP server with inputSchema requiring a 'query' string.
    server.registerTool(
      "search_skills",
      {
        description: "Filter skills by free-text query over id, title, and description.",
        inputSchema: {
          query: z.string().describe("Case-insensitive substring match"),
        },
      },
      async ({ query }) => {
        tracker?.recordToolCall("search_skills", { query });
        const found = await registry.search(query);
        const lines = found.map(
          (s) =>
            `- **${s.id}**${s.title ? `: ${s.title}` : ""}\n  ${s.description.replace(/\s+/g, " ").slice(0, 280)}`,
        );
        return {
          content: [
            {
              type: "text",
              text:
                lines.length > 0
                  ? lines.join("\n\n")
                  : `No skills matched query: ${query}`,
            },
          ],
        };
      },
    );
  • Handler function that calls registry.search() with the query and formats results as markdown bullet list.
    async ({ query }) => {
      tracker?.recordToolCall("search_skills", { query });
      const found = await registry.search(query);
      const lines = found.map(
        (s) =>
          `- **${s.id}**${s.title ? `: ${s.title}` : ""}\n  ${s.description.replace(/\s+/g, " ").slice(0, 280)}`,
      );
      return {
        content: [
          {
            type: "text",
            text:
              lines.length > 0
                ? lines.join("\n\n")
                : `No skills matched query: ${query}`,
          },
        ],
      };
    },
  • The SkillsRegistry.search() method that performs a case-insensitive substring match against id, title, and description.
      async search(query: string): Promise<SkillManifestEntry[]> {
        const q = query.trim().toLowerCase();
        const all = await this.listSkills();
        if (!q) return all;
        return all.filter((s) => {
          const blob = `${s.id}\n${s.title ?? ""}\n${s.description}`.toLowerCase();
          return blob.includes(q);
        });
      }
    }
  • Input schema for search_skills: takes a single 'query' string parameter for case-insensitive substring matching.
    {
      description: "Filter skills by free-text query over id, title, and description.",
      inputSchema: {
        query: z.string().describe("Case-insensitive substring match"),
      },
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It only describes the operation as filtering without mentioning safety (read-only), pagination, error handling, or what happens with no matches. Insufficient for a tool lacking annotations.

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?

Single sentence of 9 words, front-loaded with verb and resource, no redundant information. Efficient and to the point.

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?

Tool has only one parameter and no output schema. While the description covers input, it fails to explain return values (e.g., what fields are returned, pagination). For a straightforward search, this is adequate but not complete.

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

Parameters4/5

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

Schema coverage is 100% with a single parameter 'query' described as 'Case-insensitive substring match.' The description adds value by specifying which fields (id, title, description) are searched, going beyond the schema.

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?

Description clearly states 'Filter skills by free-text query over id, title, and description.' It specifies the verb (filter), resource (skills), and scope (fields searched), distinguishing from sibling tools get_skill and list_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 comparison to siblings or guidance on when to use vs alternatives. However, the context signals indicate siblings exist, and the purpose implies it's for searching, not retrieving a single skill or listing all.

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/amazingashis/mcp-deployment'

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