Skip to main content
Glama

list_enabled_docs

Retrieve all active documents with their cache status to manage and monitor available documentation resources.

Instructions

List all enabled docs with their cache status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
verboseNoWhether to show detailed information

Implementation Reference

  • Handler for the list_enabled_docs tool. Ensures config exists, filters enabled docs from the docs array using docConfig, reads crawl status from config, formats output based on verbose flag, and returns text content listing enabled docs with cache status.
    case "list_enabled_docs": {
      // Ensure config file exists before reading it
      await ensureConfigFile();
      
      const verbose = Boolean(request.params.arguments?.verbose);
      const config = await fs.readJson(configPath);
      const enabledDocs = docs.filter(doc => docConfig[doc.name]);
      
      const result = enabledDocs.map(doc => {
        const crawledAt = config.crawledDocs?.[doc.name] || "Not crawled";
        return verbose
          ? `${doc.name} (Enabled)\n  Start URL: ${doc.crawlerStart}\n  Last crawled: ${crawledAt}`
          : `${doc.name} [${crawledAt === "Not crawled" ? "Not cached" : "Cached"}]`;
      });
    
      return {
        content: [{
          type: "text",
          text: result.join("\n") || "No enabled docs found"
        }]
      };
    }
  • src/index.ts:502-515 (registration)
    Registration of the list_enabled_docs tool in the ListToolsRequestSchema handler, including name, description, and input schema for optional verbose boolean parameter.
    {
      name: "list_enabled_docs",
      description: "List all enabled docs with their cache status",
      inputSchema: {
        type: "object",
        properties: {
          verbose: {
            type: "boolean",
            description: "Whether to show detailed information",
            default: false
          }
        }
      }
    },
  • Input schema definition for the list_enabled_docs tool, defining an optional verbose boolean property.
    inputSchema: {
      type: "object",
      properties: {
        verbose: {
          type: "boolean",
          description: "Whether to show detailed information",
          default: false
        }
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a list operation (implying read-only) and mentions cache status, but doesn't describe what 'enabled' means, how results are formatted, whether there's pagination, or any rate limits or authentication requirements. For a tool with zero annotation coverage, this is insufficient.

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, efficient sentence with zero wasted words. It's front-loaded with the core purpose and includes a useful additional detail (cache status) without unnecessary elaboration.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete for a tool that likely returns a list of documents. It doesn't explain what 'enabled' means in this context, what cache status entails, or the structure of the returned data. For a tool with siblings like 'list_all_docs', more context is needed to guide proper usage.

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 'verbose' parameter fully documented. The description doesn't add any parameter-specific information beyond what's in the schema, such as examples of detailed vs. non-detailed output. Since schema coverage is high, 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 verb ('List') and resource ('all enabled docs'), specifying the scope of documents to include. It adds useful context about cache status, which distinguishes it from a generic list operation. However, it doesn't explicitly differentiate from sibling tools like 'list_all_docs' or 'search_docs'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'list_all_docs' or 'search_docs'. It mentions cache status, which might imply usage for monitoring, but offers no explicit when/when-not instructions or prerequisites.

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/askme765cs/open-docs-mcp'

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