Skip to main content
Glama
Sign In
himalaya-mcp

himalaya-mcp

by Data-Wise
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_folder

Delete an email folder or mailbox. Requires a confirmation flag to proceed, otherwise returns a preview warning for safe handling.

Instructions

Delete an email folder/mailbox. SAFETY: requires confirm=true to actually delete. Without confirm, returns a preview warning.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "delete_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the folder to delete
accountNoAccount name (uses default if omitted)
confirmNoSet to true to actually delete. Without this, only shows a preview warning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

A4.4/5.0
Behavior4/5

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

Discloses the critical safety mechanism (confirm flag) and preview behavior. Without annotations, this is essential. Could add permissions or consequences, but sufficient for basic safety.

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?

Two efficient sentences with key information front-loaded. No redundant text, every word adds value.

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?

Covers main behavior and all parameters. Lacks discussion of return values or errors, but acceptable for a simple deletion tool with no output schema.

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?

With 100% schema coverage, baseline is 3. The description adds concrete meaning: confirm must be true for deletion, account defaults if omitted. Enhances understanding beyond schema.

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?

Explicitly states 'Delete an email folder/mailbox' – a specific verb and resource, distinguishing it from sibling tools like create_folder and list_folders.

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?

Describes the mandatory confirm parameter for actual deletion and the preview behavior without it. Does not explicitly compare to alternatives but provides clear safety guidelines.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools