Skip to main content
Glama
YanceyOfficial

Obsidian iCloud MCP

remove_file

Deletes specific files from Obsidian vaults in iCloud Drive via the Obsidian iCloud MCP. Simplifies file management by enabling AI-assisted removal of notes or documents securely.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes

Implementation Reference

  • The primary handler function that implements the remove_file tool logic. It validates input using RemoveFileArgsSchema, unlinks the specified file using fs.unlink, and returns a success message.
    export async function removeFile(args?: Record<string, unknown>) {
      const parsed = RemoveFileArgsSchema.safeParse(args)
      if (!parsed.success) {
        throw new Error(`Invalid arguments for remove_file: ${parsed.error}`)
      }
      const result = await fs.unlink(parsed.data.path)
      return {
        content: [{ type: 'text', text: result }]
      }
    }
  • Zod schema defining the input arguments for the remove_file tool: a required 'path' string.
    export const RemoveFileArgsSchema = z.object({
      path: z.string()
    })
  • src/index.ts:121-124 (registration)
    Registration of the remove_file tool in the ListToolsRequestHandler, providing name, description (from prompt), and input schema.
      name: 'remove_file',
      description: removeFilePrompt(),
      inputSchema: zodToJsonSchema(RemoveFileArgsSchema) as ToolInput
    },
  • src/index.ts:187-189 (registration)
    Dispatch logic in the CallToolRequestHandler switch statement that routes 'remove_file' calls to the removeFile handler.
    case 'remove_file': {
      return removeFile(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