Local MCP

Create Email Folder

create_email_folder

Destructive

Creates a mailbox folder in the Mac's Apple Mail (Mail.app), in one account. If Mail has more than one account, account is required: the tool refuses to guess where the folder goes (list_email_accounts gives the names). If a folder with that name already exists it creates nothing and says so. Reports created only after it sees the folder in the account's folder list; on an Exchange account, where Mail cannot confirm the folder with the server, it answers created=false with status server_unconfirmed: use m365_create_email_folder for that mailbox.

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": "create_email_folder"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Folder name
`account`	No	Account name (optional, uses default)
`confirm`	No	Ignored; kept for older clients.

Output Schema

Name	Required	Description	Default
`name`	Yes
`status`	No
`created`	Yes
`server_confirmed`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026
- changedInput schema / properties / confirm / description
```
Previous value: -"Must be true to create"New value: +"Ignored; kept for older clients."
```
Changed2 schema fields changedOct 22, 2026
- addedOutput schema / properties / server_confirmed
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / status
```
Added value: +{
+  "enum": [
+    "server_unconfirmed"
+  ],
+  "type": "string"
+}
```
First observedJun 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the destructiveHint=false/readOnly=true annotations it discloses idempotency ('creates nothing and says so' if the name exists), a verification step ('reports created only after it sees the folder'), and the Exchange failure mode returning created=false with status server_unconfirmed.

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

Conciseness4/5

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

The scaffolding constraint and account requirement are front-loaded, and every sentence carries information. It is dense with clauses (verification, Exchange fallback) but none are waste; slightly long-winded for a create tool.

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

Completeness5/5

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

Covers prerequisites (account disambiguation), duplicate handling, confirmation semantics, and the one platform-specific failure path, and even explains the returned status field despite an output schema existing. Nothing an agent needs to call this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description adds genuine meaning by explaining that `account` becomes required when multiple accounts exist and that omitting it is refused rather than defaulted. It does not explain `confirm` being a no-op, but the schema already labels it 'Ignored'.

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?

States a specific verb (creates), resource (mailbox folder), and target platform (Mac's Apple Mail / one account). It explicitly distinguishes itself from m365_create_email_folder for Exchange mailboxes, so an agent can pick the right tool without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use rules: account is required when Mail has more than one account, the tool refuses to guess, and list_email_accounts supplies names. It also names the alternative tool and the condition (Exchange account) that routes to it.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.