Skip to main content
Glama

Check a Custom Domain

varity_domain_verify
Idempotent

Verify an app's custom domain by checking that its DNS record is in place and the domain is live.

Instructions

Check whether the DNS record for an app's custom domain is in place and whether the domain is live.

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": {
      "deployment": "<deployment>"
    },
    "name": "varity_domain_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
deploymentYesThe deployment id or app name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.1

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare openWorldHint=true (DNS lookups) and idempotentHint=true, and the description reinforces that this is a live DNS/domain check. However, it does not say what happens on a negative result, whether the tool errors or returns a status, or how long propagation checks may take. There is mild tension between "Check" and readOnlyHint=false, but the network lookups plausibly justify the annotation, so this is not a direct contradiction.

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?

One tightly written sentence with no filler that front-loads the verb and the two things being verified. It is perhaps too terse for the tool's complexity, but nothing is wasted.

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?

There is no output schema, so the description should explain what a verification result looks like (pass and fail states, DNS record states, live or not live), and it does not. For an open-world network check, that leaves an agent unable to interpret the response.

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?

There is a single required parameter with 100% schema description coverage ("The deployment id or app name"). The description mentions the app but adds no format, resolution, or ambiguity-resolution details beyond the schema, so the baseline of 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?

The description names a specific verb and resource: check the DNS record of an app's custom domain and whether the domain is live. That clearly separates it from the sibling mutation tools varity_domain_add and varity_domain_remove, though it never names them 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?

No when-to-use guidance is given at all. The agent must infer that this should run after varity_domain_add and before declaring a domain ready; nothing states prerequisites, retry behavior, or what to do if the check fails.

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