Skip to main content
Glama
Sign In
ClawAIMail

ClawAIMail

by joansongjr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

create_inbox

Create a new email inbox by providing a username. Use this to set up a dedicated inbox for your AI agent.

Instructions

Create a new email inbox (optional — a default inbox is auto-created if needed)

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": {
      "username": "<username>"
    },
    "name": "create_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesEmail username (e.g. "mybot" creates mybot@clawaimail.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions creation and auto-creation, but fails to indicate idempotency, error behavior for duplicate usernames, or authentication requirements.

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 a single sentence with no wasted words, efficiently conveying the core functionality and optionality.

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

Completeness3/5

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

The description lacks details about the return value or how the created inbox integrates with sibling tools. Given no output schema, this information would aid completeness, but the basic purpose is covered.

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

Parameters3/5

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

The schema covers the single parameter with 100% description coverage, including an example. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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

Purpose4/5

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

The description clearly states it creates a new email inbox and notes it is optional due to auto-creation. It distinguishes from sibling tools like delete_inbox and list_inboxes.

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

Usage Guidelines3/5

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

The description implies usage when a custom inbox is needed, mentioning a default is auto-created. However, it does not explicitly state when to use this tool versus relying on the default or compare with siblings.

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