Skip to main content
Glama
YanceyOfficial

Obsidian iCloud MCP

create_directory

Set up or verify directory structures for projects by creating new or nested directories in one operation. Ensures required paths exist silently within allowed directories on the Obsidian iCloud MCP server.

Instructions

Create a new directory or ensure a directory exists. Can create multiple nested directories in one operation. If the directory already exists, this operation will succeed silently. Perfect for setting up directory structures for projects or ensuring required paths exist. Only works within allowed directories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes

Implementation Reference

  • Implements the create_directory tool by parsing args with schema, creating directory with fs.mkdir (recursive), and returning success message.
    export async function createDirectory(args?: Record<string, unknown>) {
      const parsed = CreateDirectoryArgsSchema.safeParse(args)
      if (!parsed.success) {
        throw new Error(`Invalid arguments for create_directory: ${parsed.error}`)
      }
      await fs.mkdir(parsed.data.path, { recursive: true })
      return {
        content: [
          {
            type: 'text',
            text: `Successfully created directory ${parsed.data.path}`
          }
        ]
      }
    }
  • Zod schema defining input for create_directory: object with 'path' string.
    export const CreateDirectoryArgsSchema = z.object({
      path: z.string()
    })
  • src/index.ts:130-134 (registration)
    Registers the 'create_directory' tool in ListToolsRequestHandler with name, prompt-based description, and schema.
    {
      name: 'create_directory',
      description: createDirectoryPrompt(),
      inputSchema: zodToJsonSchema(CreateDirectoryArgsSchema) as ToolInput
    },
  • src/index.ts:195-197 (registration)
    Dispatches calls to 'create_directory' tool by invoking the createDirectory handler function in CallToolRequestHandler.
    case 'create_directory': {
      return createDirectory(args)
    }
Behavior4/5

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

With no annotations provided, the description carries the full burden and does so well. It discloses key behavioral traits: idempotency ('if the directory already exists, this operation will succeed silently'), ability to create nested directories, and a constraint ('only works within allowed directories'). It does not mention permissions, rate limits, or error conditions, leaving some gaps.

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 appropriately sized and front-loaded, with the core functionality stated first. Each sentence adds value: idempotency, use cases, and constraints. There is no redundant or wasted text, making it efficient and easy to parse.

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 moderate complexity (creation with idempotency and constraints), no annotations, no output schema, and low schema coverage, the description is mostly complete. It covers purpose, behavior, and usage well, but lacks details on error handling, return values, or specific path format requirements, leaving minor gaps.

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 schema has 1 parameter with 0% description coverage, so the description must compensate. It adds meaning by implying the 'path' parameter specifies the directory location and can include nested structures ('create multiple nested directories'), though it does not detail format or constraints. This partially compensates for the schema gap.

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 the specific action ('create a new directory or ensure a directory exists') and distinguishes it from siblings like 'list_directory' or 'remove_directory'. It specifies the resource ('directory') and scope ('within allowed directories'), making the purpose unambiguous.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('setting up directory structures for projects or ensuring required paths exist'), but does not explicitly state when not to use it or name alternatives. It implies usage for creation and existence-checking, which helps differentiate from siblings like 'remove_directory'.

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/YanceyOfficial/obsidian-mcp'

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