Skip to main content
Glama

Cnamio

Check a domain

check_domain
Read-only

Read-only. Finds where a domain's DNS is hosted and how it can be connected: provider, setupType, connectMethods (api_token when the records can be created with the user's provider token), nameservers, recordState for a single CNAME, and conflicts with records already published.

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

Input Schema

NameRequiredDescriptionDefault
domainYes
dnsRecordsYesRecords your product needs. host is relative to the zone; placeholders {DOMAIN}, {SUBDOMAIN}, {SLD}, {TLD}; @ is the apex (no CNAME at the apex).
checkConflictsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so 'Read-only' adds little; the value is in enumerating what the response contains and what api_token means. It does not explain the effect of checkConflicts (defaulting to true) or what a conflict result implies, leaving a gap for a diagnostic tool.

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?

A single dense sentence front-loaded with the read-only trait, followed by an ordered list of returned fields. Efficient with no filler, though the long parenthetical about api_token slightly obscures the scan.

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?

No output schema exists, so listing the returned fields is genuinely necessary and done well. However, for a tool whose result depends on caller-supplied records and a conflict-check flag, the silence on parameters and conflict semantics leaves the definition only partially complete.

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?

With only 33% schema description coverage, the description should compensate but says nothing about the three parameters. checkConflicts has no schema description at all and is only obliquely referenced via 'conflicts with records already published'; domain and the dnsRecords placeholder syntax are left entirely to the schema.

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 ('Finds where a domain's DNS is hosted') plus the diagnostic payload it inspects (provider, setupType, connectMethods, nameservers, recordState, conflicts). This clearly separates it from mutation siblings like connect_domain, though no sibling is named explicitly.

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 'Read-only' framing implies this is the inspection step before connecting, but the description never says when to use this versus connect_domain, recheck_propagation, or get_connection_status. Usage must be inferred from the output fields listed.

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