Skip to main content
Glama

Trigger a DNS check

check_domain_dns

Ask Clerk to re-check a domain's DNS records now. Returns the same verification status as get_domain_status plus domain_id and last_run_at (epoch milliseconds of the last check). If a check is already running, returns status "in_progress" instead. Follow progress with get_domain_status.

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": {
      "application_id": "<application_id>",
      "domain": "<domain>"
    },
    "name": "check_domain_dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain's name, such as example.com, or its ID (dmn_…), as list_domains returns them.
application_idYesClerk application ID (app_…).

Output Schema

NameRequiredDescriptionDefault
dnsNo
sslNo
mailNo
proxyNo
statusYes
messageNo
domain_idNo
last_run_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / last_run_at / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / last_run_at / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"Domain name or domain ID (dom_…)."New value: +"The domain's name, such as example.com, or its ID (dmn_…), as list_domains returns them."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "dns": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "status": {
      +              "type": "string"
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "domain_id": {
      +      "type": "string"
      +    },
      +    "last_run_at": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "mail": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "status": {
      +              "type": "string"
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "proxy": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "status": {
      +              "type": "string"
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "ssl": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "status": {
      +              "type": "string"
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "status": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status"
      +  ],
      +  "type": "object"
      +}
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

With annotations already declaring the non-readOnly, non-idempotent, non-destructive profile, the description still adds real value: the concurrency behavior (returns "in_progress" if a check is already running) and the extra fields returned versus get_domain_status. It omits auth/scoping requirements and whether repeated triggers are throttled, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the action, then the return contract, then the concurrency caveat, then the follow-up pointer. Every sentence carries information an agent needs.

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 two-param trigger tool with full schema coverage, annotations, and an output schema, the description covers action, return shape, concurrency, and the follow-up path. The return-value summary partially duplicates the output schema, but that redundancy is what makes the get_domain_status distinction usable.

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?

Schema coverage is 100% and the schema already documents that domain accepts a name or a dmn_ ID and that application_id is an app_ ID. The description adds no format or edge-case detail beyond this, so the baseline 3 applies.

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

Purpose5/5

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

"Ask Clerk to re-check a domain's DNS records now" gives a specific verb (re-check) and resource (DNS records), and explicitly contrasts the return payload with get_domain_status. An agent can immediately tell this is the trigger tool versus the status-reader sibling.

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 states when to call this (to force a fresh check) and routes follow-up polling to get_domain_status, so the trigger/poll split is clear. It does not state when *not* to use it (e.g., just reading a cached status), leaving that one inference to the agent.

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