Skip to main content
Glama

list_docsets

List all installed documentation sets to view docset IDs, names, and installation details for quick reference and management.

Instructions

List all installed documentation sets (docsets). Shows docset IDs, names, and installation details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.js:336-344 (registration)
    Tool registration in ListToolsRequestSchema handler. Defines the 'list_docsets' tool with name, description, and empty input schema.
    {
      name: 'list_docsets',
      description: 'List all installed documentation sets (docsets). Shows docset IDs, names, and installation details.',
      inputSchema: {
        type: 'object',
        properties: {},
        additionalProperties: false
      }
    },
  • Handler for the 'list_docsets' tool in CallToolRequestSchema switch. Calls this.docsetService.listDocsets(), formats the list with name, ID, path, and installation date, or shows a message if none are installed.
    case 'list_docsets':
      const docsets = await this.docsetService.listDocsets();
      
      if (docsets.length === 0) {
        return {
          content: [{
            type: 'text',
            text: 'No docsets installed yet.\n\nUse `add_docset` to install documentation sets for your frameworks and libraries.'
          }]
        };
      }
      
      let output = `# Installed Documentation Sets\n\nFound ${docsets.length} docset(s):\n\n`;
      docsets.forEach((docset, index) => {
        output += `## ${index + 1}. ${docset.name}\n`;
        output += `**ID:** ${docset.id}\n`;
        output += `**Path:** ${docset.path}\n`;
        output += `**Installed:** ${new Date(docset.downloadedAt).toLocaleString()}\n\n`;
      });
      
      return {
        content: [{
          type: 'text',
          text: output
        }]
      };
  • The DocsetService.listDocsets() helper method. Returns an array of all docset metadata objects stored in the internal Map.
    async listDocsets() {
      return Array.from(this.docsets.values());
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states it lists and shows IDs, names, and details, but omits that it is read-only, safe, and returns a list. The lack of behavioral context is a gap.

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 a single sentence with no redundancy. It is front-loaded and every word adds value.

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 simplicity (no parameters, no output schema), the description adequately states what is listed. It could mention that the output is an array, but that is minor.

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?

The tool has no parameters, and the baseline is 4. The description adds no parameter information, which is acceptable since schema coverage is 100% and no parameters exist.

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 uses specific verb 'list' and resource 'docsets', clearly identifying its action. It distinguishes from sibling tools like add_docset and remove_docset by stating it shows all installed documentation sets.

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 implies use when needing to see installed docs, but does not explicitly state when to use or not use it. No alternatives or exclusions are mentioned.

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/afterxleep/doc-bot'

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