Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Create domain

create_domain

Add a sending domain to a specific pod so agents can send email from it. Requires the pod ID and domain name; the server rejects IDs outside the key's scope.

Instructions

Add a sending domain to the pod.

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_domain"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false, so the mutation and non-idempotency profile is carried by structured data. The description adds only the qualifier 'sending', which hints at an email/DNS context but does not explain that creation likely requires subsequent verification, what permissions the key needs, or whether a duplicate create errors or duplicates.

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 front-loaded sentence with the verb first and zero filler. It is efficient, though its brevity leaves it closer to a title restatement than a structured definition with usage or behavioral notes.

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

Completeness2/5

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

For a two-parameter create tool with no output schema, the description omits the essentials: what a successful call returns (domain object, setup link, DNS records), the verification workflow implied by the sibling tools, and error behavior for duplicates or out-of-scope pod ids. Annotations cover safety signals but not the operational context an agent needs to sequence this call.

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?

Schema coverage is 50%: pod_id is documented in the schema, domain is not. The description implicitly maps both — the domain being added and the pod it is added to — but adds no format, normalization, or validation detail for the undocumented domain parameter, so it only marginally compensates for the coverage gap.

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 gives a specific verb and resource — 'Add a sending domain' — and scopes it to a pod, which distinguishes it from get_domain, verify_domain, and delete_domain by name alone. It stops short of naming any sibling or contrasting scope, so it is clear but not explicitly differentiated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite (e.g. DNS records, plan limits), and no statement about what to do if the domain already exists. The reader must infer the whole usage context from the verb 'Add'.

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