Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Update domain

update_domain
Idempotent

Update settings for an email domain scoped to a pod. Use it to change domain configuration while access stays limited to IDs your key can reach.

Instructions

Update a domain's settings.

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_id": "<domain_id>"
    },
    "name": "update_domain"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing on top of that: it doesn't say which settings are mutable, whether omitted fields are preserved, what permissions are needed, or what the effect of a partial payload is.

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

Conciseness3/5

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

A single short sentence is maximally concise, but here brevity is achieved by omission rather than by density. There is no wasted wording, yet the sentence also carries no information an agent could act on beyond the tool name.

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 non-destructive but still mutating tool with an undocumented required parameter and no output schema, the description is too thin. An agent cannot determine what payload to send or what the result means, leaving core gaps that the annotations do not fill.

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

Parameters2/5

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

With only 50% schema coverage, the description should compensate, but it says nothing about either parameter. domain_id is undocumented in both places, and the description gives no hint that the body can carry settings fields at all — additionalProperties is false, so it is unclear what updatable fields even exist.

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

Purpose3/5

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

"Update a domain's settings" names a specific verb and resource, so the general intent is clear. However, "settings" is left entirely unspecified — no fields, no scope — and nothing distinguishes it from siblings like update_inbox, update_label, or update_webhook beyond the resource noun.

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 prerequisites, and no mention of alternatives such as create_domain, delete_domain, or verify_domain. The agent must infer entirely on its own that this is the mutation path for an existing domain.

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