Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Verify domain

verify_domain
Idempotent

Triggers DNS verification for a domain to confirm ownership or DNS configuration within a permission-scoped pod.

Instructions

Trigger DNS verification for a domain.

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": "verify_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.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the agent knows this is a repeatable non-destructive external-facing operation. The description adds almost nothing beyond the name and title: it does not say whether the check is asynchronous, whether a result is returned immediately, whether repeated calls are safe, or how to retrieve the verification outcome. Given that annotations cover the safety profile, the description's contribution above them is minimal.

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?

It is a single short, front-loaded sentence with no filler or redundancy. The tradeoff is that the terseness borders on under-specification rather than tightness, keeping it just below the top mark.

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 mutating, externally-facing verification trigger with no output schema, the description is too thin. An agent cannot tell whether verification results come back in the response, must be polled elsewhere, or how long the check takes, and one of the two required parameters is undocumented.

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?

Schema description coverage is only 50%: pod_id is documented in the schema (including the key-scope constraint), but domain_id has no description anywhere. The phrase "for a domain" does not clarify whether domain_id is a numeric id, a domain name, or a UUID, nor what format is expected. The description fails to compensate for the undocumented parameter.

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 names a specific action and resource: "Trigger DNS verification for a domain." That distinguishes it from create_domain/update_domain/get_domain, which are CRUD operations on the domain object rather than a verification trigger. It stops short of explicitly contrasting with those siblings, 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 Guidelines2/5

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

There is no guidance on when this tool should be used instead of alternatives. It does not mention prerequisites (for example, that the domain must exist and its DNS records must be configured first), nor what to do afterwards, nor when to prefer a plain status lookup.

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