Skip to main content
Glama

Cnamio

Connect a domain (manual records)

connect_domain

Starts a manual connection: returns the exact records the domain owner must create at their DNS provider and starts watching propagation on the authoritative nameservers (up to 72 hours). Does not change DNS. Follow it with get_connection_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": {
      "domain": "<domain>",
      "dnsRecords": "<dnsRecords>"
    },
    "name": "connect_domain"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, and the description adds the critical clarification "Does not change DNS" — the mutation is only internal state, which an agent could easily misread from the write annotation. It also discloses the async watching behavior and 72-hour horizon. It stops short of addressing what a repeat call does (idempotentHint=false) or any auth requirements.

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 what the tool does, followed by the key negative constraint and the required next step. No filler and nothing repeated from the schema or title.

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?

With no output schema, the description correctly covers returns (the resolved records to hand over) and the lifecycle (start watching, then poll with get_connection_status). Annotations carry the safety profile. Remaining omissions — duplicate-call behavior and error handling — are minor for this tool's complexity.

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 description coverage is 67%, so much is already documented: dnsRecords carries placeholder rules, apex constraints, and the userId description explains webhook echoing. The description clarifies the input/output relationship (you supply needed records, it returns the exact records the owner must create) but adds nothing about the domain parameter's expected shape or the retry semantics of dnsRecords.

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?

"Starts a manual connection" gives a concrete verb and resource, and the word "manual" implicitly contrasts with the sibling connect_domain_automatic. It also states what the call produces (the exact records the owner must create). The only gap is that the automatic sibling is never named outright, so differentiation relies on inference from the adjective.

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?

Explicitly routes the agent forward: "Follow it with get_connection_status," and the 72-hour propagation window tells the agent the flow is long-running. There is no explicit statement of when to prefer this over connect_domain_automatic, though "manual" implies the case where records must be handed to the domain owner.

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