Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Create inbox

create_inbox

Create a new email inbox on one of a pod's own verified domains. Use a pod ID and verified domain to provision a permission-scoped inbox for a pod.

Instructions

Create a new inbox in the pod, on one of the pod's own VERIFIED domains (domain is required; an inbox on the platform domain cannot be created with an API key).

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

Input Schema

NameRequiredDescriptionDefault
domainYes
pod_idYesA pod id the key can reach. The server rejects any id outside this key's scope.
usernameNo
display_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, and the description adds real behavioral context on top: a hard server-side constraint about which domains qualify and an API-key-specific restriction. It does not cover failure modes such as duplicate usernames or what happens when the domain is unverified, which keeps it below a 5.

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?

A single sentence with the core action front-loaded and the constraint in a parenthetical. Dense but every clause carries information; the backticked parameter reference is slightly awkward but not wasteful.

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?

For a four-parameter creation tool with no output schema, the description covers the risky part of the call (domain eligibility and key scope). It omits any hint of the returned object and the semantics of the optional username/display_name fields, leaving a modest but real gap.

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?

With schema coverage at 25%, only pod_id is documented in the schema; the description usefully compensates for `domain` by stating it is required and must be a verified pod domain. The `username` and `display_name` parameters remain unexplained in both places, so the gap is only partly closed.

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?

States a specific verb and resource ("Create a new inbox in the pod") plus the domain constraint, which is enough to distinguish it from delete_inbox and update_inbox without opening a schema. It stops short of naming siblings explicitly, so it is clear but not fully differentiated.

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 supplies an important precondition (the domain must be one of the pod's own verified domains, and the platform domain is not creatable via API key), which effectively tells the agent when this call will succeed. It gives no guidance on when to prefer update_inbox or list_inboxes, so usage context is implied rather than spelled out.

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