Skip to main content
Glama
amazingashis

skills-mcp-server

by amazingashis

list_skills

Lists all available skills with their ID, title, and a short description teaser.

Instructions

Return a manifest of available skills (id, title, description teaser). No filesystem paths are exposed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the list_skills tool. It calls registry.listSkills(), formats results as a markdown list (id, title, description teaser), and returns the text content.
    async () => {
      tracker?.recordToolCall("list_skills", {});
      const skills = await registry.listSkills();
      const lines = skills.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 found. Mount SKILL.md files under SKILLS_ROOT (see server README).",
          },
        ],
      };
    },
  • The list_skills tool is registered via server.registerTool with name 'list_skills', a description, empty inputSchema, and the handler callback.
    server.registerTool(
      "list_skills",
      {
        description:
          "Return a manifest of available skills (id, title, description teaser). No filesystem paths are exposed.",
        inputSchema: {},
      },
      async () => {
        tracker?.recordToolCall("list_skills", {});
        const skills = await registry.listSkills();
        const lines = skills.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 found. Mount SKILL.md files under SKILLS_ROOT (see server README).",
            },
          ],
        };
      },
    );
  • The list_skills tool has an empty input schema (no parameters required).
    inputSchema: {},
  • The SkillsRegistry.listSkills() method is the core helper that walks the skills directory for SKILL.md files, extracts title/description teaser from markdown, and returns sorted SkillManifestEntry[].
    async listSkills(): Promise<SkillManifestEntry[]> {
      const root = this.skillsRoot;
      let stat;
      try {
        stat = await fs.stat(root);
      } catch {
        return [];
      }
      if (!stat.isDirectory()) return [];
    
      const files = await walkSkillFiles(root);
      const out: SkillManifestEntry[] = [];
    
      for (const filePath of files) {
        const relDir = path.relative(root, path.dirname(filePath));
        /** SKILL.md directly under SKILLS_ROOT */
        const normalizedId = relDir === "" ? "_root" : toPosix(relDir);
    
        let raw: string;
        try {
          raw = await fs.readFile(filePath, "utf8");
        } catch {
          continue;
        }
        const { title, description } = extractTitleAndTeaser(raw);
        out.push({
          id: normalizedId,
          filePath,
          title,
          description,
        });
      }
    
      out.sort((a, b) => a.id.localeCompare(b.id));
      return out;
    }
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses that no filesystem paths are exposed, implying safety. However, it does not mention auth requirements, rate limits, or other behavioral aspects. For a simple read operation, this is sufficient.

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 two sentences, front-loaded with the primary purpose, and adds a concise safety note. Every word earns its place with no fluff.

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

Completeness5/5

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

Given the tool's extreme simplicity (no params, no output schema), the description adequately explains the return fields and a key behavioral trait. It provides sufficient context for an agent to invoke correctly, despite not contrasting with siblings.

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?

No parameters exist; schema coverage is 100%. According to guidelines, zero parameters yield a baseline of 4. The description adds no parameter info as there are none, which is appropriate.

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 it returns a manifest of available skills with specific fields (id, title, description teaser). It uses a specific verb 'Return' and resource 'manifest of available skills', and implicitly distinguishes from siblings like get_skill (single) and search_skills (filtered).

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 does not explicitly state when to use this tool versus alternatives (get_skill, search_skills). The context implies it is for listing all skills, but no guidance on when to choose it over the others is provided.

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