Skip to main content
Glama
dazeb

Markdown Downloader

create_subdirectory

Organize downloaded markdown files by creating a new subdirectory in the root folder. Specify the directory name to efficiently structure and manage stored webpage content.

Instructions

Create a new subdirectory in the root download folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the subdirectory to create

Implementation Reference

  • Handler function for the 'create_subdirectory' tool. Validates the input name parameter, retrieves the download directory from config, constructs the full path, creates the subdirectory using fs.ensureDir, and returns a success message or error.
    // Create subdirectory
    if (request.params.name === 'create_subdirectory') {
      const subdirectoryName = request.params.arguments?.name;
    
      if (!subdirectoryName || typeof subdirectoryName !== 'string') {
        throw new McpError(
          ErrorCode.InvalidParams,
          'A valid subdirectory name must be provided'
        );
      }
    
      try {
        const config = getConfig();
        const newSubdirectoryPath = path.join(config.downloadDirectory, subdirectoryName);
    
        // Create the subdirectory
        await fs.ensureDir(newSubdirectoryPath);
    
        return {
          content: [
            {
              type: 'text',
              text: `Subdirectory created: ${newSubdirectoryPath}`
            }
          ]
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : 'Unknown error';
        return {
          content: [
            {
              type: 'text',
              text: `Failed to create subdirectory: ${errorMessage}`
            }
          ],
          isError: true
        };
      }
    }
  • Input schema definition for the 'create_subdirectory' tool, specifying the required 'name' parameter as a string.
    inputSchema: {
      type: 'object',
      properties: {
        name: {
          type: 'string',
          description: 'Name of the subdirectory to create'
        }
      },
      required: ['name']
    }
  • src/index.ts:167-180 (registration)
    Registration of the 'create_subdirectory' tool in the ListTools response, including name, description, and input schema.
    {
      name: 'create_subdirectory',
      description: 'Create a new subdirectory in the root download folder',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Name of the subdirectory to create'
          }
        },
        required: ['name']
      }
    }
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 the tool creates a subdirectory, implying a write operation, but doesn't specify whether this requires permissions, what happens if the subdirectory already exists, or if there are rate limits. This is a significant gap for a mutation tool with zero annotation coverage.

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 that directly states the tool's purpose without any unnecessary words. It is front-loaded with the core action and location, making it easy for an agent to parse quickly. Every part of the sentence earns its place.

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 the tool's complexity as a mutation operation with no annotations and no output schema, the description is incomplete. It doesn't address potential errors, return values, or behavioral nuances like overwrite policies. For a tool that modifies the filesystem, this lack of context is inadequate.

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 'name' parameter clearly documented. The description adds no additional parameter semantics beyond what the schema provides, such as naming constraints or examples. Since the schema does the heavy lifting, 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 action ('Create a new subdirectory') and specifies the location ('in the root download folder'), which distinguishes it from sibling tools like 'set_download_directory' or 'list_downloaded_files'. However, it doesn't explicitly differentiate from 'get_download_directory' in terms of creation vs. retrieval, which prevents a perfect score.

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 'set_download_directory' or 'get_download_directory'. It lacks any mention of prerequisites, such as needing the root download folder to exist, or exclusions, such as not being able to create nested subdirectories beyond the root. This leaves the agent with minimal context for decision-making.

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

Related 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/dazeb/markdown-downloader'

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