Skip to main content
Glama

Cnamio

Connect a domain with the provider token

connect_domain_automatic

Creates the records at the domain's DNS provider with an API token the domain owner provides (only when check_domain returned connectMethods containing api_token). The token is used during this call only and is never stored; existing records are never changed or deleted (a conflict returns 409 with the reasons). Never ask for or use DNS provider passwords.

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>",
      "providerToken": "<providerToken>"
    },
    "name": "connect_domain_automatic"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
userIdNo
dnsRecordsYesRecords your product needs. host is relative to the zone; placeholders {DOMAIN}, {SUBDOMAIN}, {SLD}, {TLD}; @ is the apex (no CNAME at the apex).
providerTokenYesThe domain owner's API token for their DNS provider.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Substantially exceeds the annotations by disclosing that the token is transient and never stored, that existing records are never modified or deleted, and that conflicts surface as 409 with reasons. The only unexplained area is repeat-invocation behavior, which matters given idempotentHint=false.

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 tight sentences: operation first, precondition and token handling next, safety guarantee and error code last. No filler; every clause carries operational information.

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?

Covers gating, credential handling, non-destructiveness, and the conflict response for an open-world mutation tool with no output schema. It stops short of saying what a successful call returns or whether re-running is safe, which is the remaining gap for a non-idempotent write.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, but the description adds real meaning for providerToken (owner's token, used only for this call, not persisted) on top of a schema that already documents dnsRecords and placeholders richly. userId remains undocumented in both description and schema.

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?

States a specific verb and resource ('Creates the records at the domain's DNS provider') plus the distinguishing mechanism (API token supplied by the domain owner), which separates it from the manual connect_domain path without needing the sibling named. An agent can tell what this does and how it differs from the token-less alternative.

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

Usage Guidelines5/5

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

Gives a verifiable precondition: use only when check_domain returned connectMethods containing api_token. It also adds an explicit prohibition ('Never ask for or use DNS provider passwords'), covering both the when and the when-not case.

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