Skip to main content
Glama

Check a custom domain

check_domain
Idempotent

Checks whether the site's custom domain is live and says in plain words what is still missing (DNS records or the security certificate). A domain counts as live only when both the domain and its security certificate are active. This call updates the stored status and, when the domain becomes active on a published site, the free mywebdesk.app address forwards visitors to it. A domain still waiting for DNS after 7 days is removed, and the result's notices say so.

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": {
      "site_id": "<site_id>"
    },
    "name": "check_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site id from list_sites or create_site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond annotations: it discloses that the call is not a pure read ('updates the stored status'), that a becoming-active domain changes visitor forwarding from the free mywebdesk.app address, and that a domain awaiting DNS for 7 days is removed with a notice. Those are exactly the side effects an agent could not infer from readOnlyHint=false and destructiveHint=false.

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?

Front-loaded with the core question ('is it live and what's missing') before the side-effect details, and each sentence contributes a distinct fact. Slightly dense, but no filler.

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 one-parameter tool with no output schema, the description covers purpose, liveness criteria, side effects, and characterizes the result ('the result's notices say so'). Only the exact result shape remains unspecified, which is acceptable since it can be observed at call time.

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?

The single parameter site_id already has full schema description coverage and the description adds no syntax, format, or sourcing detail beyond it. With coverage at 100%, the schema carries the parameter semantics, so baseline 3 applies.

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: checks whether the site's custom domain is live and reports what is missing (DNS records or certificate). This clearly distinguishes it from a connection/mutation tool, but it never names connect_domain or another sibling, so the differentiation is inferred rather than explicit.

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 gives the criteria for a live domain and the 7-day DNS timeout, which implies this is a polling/verification call, but it never states when to call it versus connect_domain or that it should follow a connection attempt. Usage 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources