Skip to main content
Glama

domains_check_domain_delegation

Read-onlyIdempotent

Check whether a domain is owned by the caller, registered in billing, and fully delegated to the correct nameservers before managing DNS or server resources.

Instructions

Checks whether the given domain belongs to the caller, is registered in billing, and is fully delegated to our nameservers. POST /domains/check-delegation

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": {
      "body": "<body>"
    },
    "name": "domains_check_domain_delegation"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real value by spelling out the three semantic checks performed, which is more than the annotations convey. It does not disclose what the response looks like, whether partial failures are reported per-condition, or whether ownership/billing failures return an error instead of a negative result.

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?

The first sentence is dense and front-loaded with the actual semantics. The trailing 'POST /domains/check-delegation' line is raw transport detail that adds little for tool selection, but it is short and does not bury the key information.

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?

With no output schema, the description should clarify what a result means — a single boolean, a per-condition breakdown, or an error when ownership fails. It conveys the three inputs to the judgment but leaves the agent guessing about the shape and interpretation of the answer, and says nothing about authorization requirements.

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 0% and the single parameter is a nested body object with a required 'name' field. The description only implies that 'name' is the domain in question; it gives no format expectations (bare apex vs. subdomain vs. trailing dot, IDN handling) nor any other constraint on the body.

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 (checks) and resource (domain delegation) and enumerates the three exact conditions evaluated: caller ownership, billing registration, and full delegation to the provider's nameservers. That level of specificity separates it in practice from siblings like domains_check_domain_available, but it never names or contrasts an alternative explicitly.

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 to call this versus domains_check_domain_available, domains_get_expected_nameservers, or domains_verify, and no stated preconditions (for example, that the domain must already be registered). The intended pre-flight/troubleshooting context is only inferable from the check contents.

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