Skip to main content
Glama
sweetrb

apple-mail-mcp

by sweetrb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create-mailbox

Create a new mailbox or folder in a specified email account, and receive confirmation once it has been created.

Instructions

Use when: creating a new mailbox/folder in an account. Returns: a confirmation that the mailbox was created. Do not use when: renaming an existing one (use rename-mailbox) or deleting one (use delete-mailbox). Use list-mailboxes to see what already exists. Safety: creates a real folder in the mail account — confirm the name and target account first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
accountNoAccount to create the mailbox in

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.10.24
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv2.10.8
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
  3. Addedv2.9.0
  4. Removedv2.8.10
  5. First observedv2.6.1

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations provided, the description discloses that the tool 'creates a real folder' and includes a safety warning to confirm name and target account. It also states the return value is a confirmation. This covers the key side effect, though it omits details like permissions or duplicate handling.

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 front-loaded with the primary use case, followed by return info, exclusions, and a safety reminder. Every sentence is purposeful and no redundant text exists.

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 simplicity and the presence of an output schema, the description covers creation, return value, alternatives, and safety. It could mention error cases or uniqueness requirements, but it is sufficiently complete for an agent to use it correctly.

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 covers 'account' with a description but not 'name' (50% coverage). The description adds context by referencing 'name and target account' in the safety note and clarifying the purpose of the main parameter. It does not fully specify name constraints, but the schema's minLength provides some guidance.

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 action: 'creating a new mailbox/folder in an account.' It distinguishes from sibling tools by explicitly naming rename-mailbox and delete-mailbox as alternatives.

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?

Provides explicit 'Use when:' and 'Do not use when:' guidance, naming specific alternatives (rename-mailbox, delete-mailbox) and recommending list-mailboxes to check existing mailboxes. This gives the agent clear decision criteria.

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