Skip to main content
Glama
YanceyOfficial

Obsidian iCloud MCP

remove_multiple_directory

Delete multiple directories at once by specifying their paths. Simplify file management for Obsidian vaults stored in iCloud Drive, enhancing organization and efficiency.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathsYes

Implementation Reference

  • Core handler function that validates input args using the schema, removes multiple directories asynchronously using rimraf on each path in parallel, and returns the results in a standardized content format. Note: contains a bug in the error message referring to 'edit_file' instead of the correct tool name.
    export async function removeMultipleDirectory(args?: Record<string, unknown>) {
      const parsed = RemoveMultipleDirectoryArgsSchema.safeParse(args)
      if (!parsed.success) {
        throw new Error(`Invalid arguments for edit_file: ${parsed.error}`)
      }
      const result = await Promise.all(
        parsed.data.paths.map((path) => rimraf(path))
      )
    
      return {
        content: [{ type: 'text', text: result }]
      }
    }
  • Zod schema defining the input for the tool: an object containing an array of strings representing directory paths to remove.
    export const RemoveMultipleDirectoryArgsSchema = z.object({
      paths: z.array(z.string())
    })
  • src/index.ts:146-151 (registration)
    Registers the tool in the ListToolsRequest handler, specifying the tool name, a description generated from a prompt function, and the input schema converted to JSON schema.
      name: 'remove_multiple_directory',
      description: removeMultipleDirectoryPrompt(),
      inputSchema: zodToJsonSchema(
        RemoveMultipleDirectoryArgsSchema
      ) as ToolInput
    },
  • src/index.ts:207-209 (registration)
    In the CallToolRequest switch statement, dispatches execution to the removeMultipleDirectory handler function when the tool name matches.
    case 'remove_multiple_directory': {
      return removeMultipleDirectory(args)
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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