Skip to main content
Glama

Check custom domain DNS

check_domain

Run a DNS check of a custom domain now; one check after the DNS records exist is enough. Status: pending_dns, verifying, active, lost. A repeat within seconds answers 429.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
typeNo
hostnameNoInstead of type, namespace and id
namespaceNo
ownerTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / hostname / description
      Previous value: -"Custom domain as a bare hostname, e.g. www.example.com; instead of type, namespace and id"New value: +"Instead of type, namespace and id"
    • removedInput schema / properties / id / description
      Removed value: -"Publication ID"
    • removedInput schema / properties / namespace / description
      Removed value: -"Publication namespace"
    • removedInput schema / properties / ownerToken / description
      Removed value: -"By publication: a profile token or an owner token added to the profile. By hostname: an admin profile token. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
    • removedInput schema / properties / type / description
      Removed value: -"Publication type; with namespace and id, instead of hostname"
  2. Changed2 schema fields changed
    • changedInput schema / properties / hostname / description
      Previous value: -"Custom domain, e.g. www.example.com; instead of type, namespace and id"New value: +"Custom domain as a bare hostname, e.g. www.example.com; instead of type, namespace and id"
    • changedInput schema / properties / ownerToken / description
      Previous value: -"By publication: an owner token in the profile. By hostname: an admin token of the profile. Default: env BREWPAGE_OWNER_TOKEN (local server only)."New value: +"By publication: a profile token or an owner token added to the profile. By hostname: an admin profile token. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations mark this as non-read-only and non-destructive, and the description adds useful behavior beyond that: it lists possible statuses and discloses the 429 rate-limit response. It does not explain side effects or whether the check changes domain state, but the key operational traits are covered.

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

Conciseness5/5

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

The description is three compact sentences with the action front-loaded, followed by timing guidance and status/rate-limit details. Every sentence adds operational value without repetition.

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?

It covers the check action, statuses, and rate limiting, which is useful for a tool with no output schema. However, with five parameters and low schema coverage, it is incomplete about how to identify the domain and what the check returns beyond status names.

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 20%, so the description should compensate for five parameters, but it does not mention id, hostname, type, namespace, or ownerToken. It only refers generally to a custom domain, leaving parameter usage largely undocumented.

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 states a specific verb and resource: run a DNS check of a custom domain now. It is clearly distinguishable from sibling domain-management tools such as set_domain and remove_domain, though it does not explicitly name an alternative.

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

Usage Guidelines4/5

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

It gives clear usage context: one check after DNS records exist is enough, and repeats within seconds return 429. It does not explicitly compare against alternatives, but the timing and rate-limit guidance are actionable.

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.