Skip to main content
Glama

Connect a domain I already own

conectar_dominio_existente
Idempotent

Use this when the person already owns a domain at another provider and wants it to show their palimpalem website. Requires palimpalem sign-in. Returns exactly two DNS steps to make at their provider; with check=true it verifies them by DNS lookup and, when both are correct, asks palimpalem to activate the domain. It never writes into DNS zones by itself. For a domain managed by palimpalem it e-mails the owner a confirmation link instead, and the change is made only after the owner clicks it.

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

Input Schema

NameRequiredDescriptionDefault
webNoOptional when the account has one website. The website: its name, its palimpalem address or its own domain.
checkNotrue to verify the two DNS steps after the person made them.
domainYesThe domain the person owns, e.g. panaderia-ruzafa.es.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the sign-in prerequisite, that the tool returns exactly two DNS steps, that check=true performs a DNS lookup and triggers activation only when both records are correct, and that it never writes into DNS zones itself. It also discloses the divergent path for palimpalem-managed domains, where an e-mail confirmation link gates the change.

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?

Nearly every sentence carries operative information and the primary trigger is front-loaded. The palimpalem-managed e-mail branch is appended at the end rather than flagged up front as an alternative path, which costs a little scanability but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description states what the call returns (the two DNS steps) and what changes on the check=true path, so an agent can act and explain results without extra fields. For a mutating, externally-facing onboarding tool this covers the necessary ground.

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 100%, so the parameters are already documented, but the description still adds meaning: it explains that check=true is used after the person has made the two DNS steps and that verification is done by DNS lookup with activation as a consequence. Only the web parameter's role (defaulting when the account has one site) is 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?

The description names a concrete scenario and outcome: a person who already owns a domain at another provider wants it pointed at their palimpalem website. That implicitly separates it from registration-style siblings such as solicitar_dominio, but no sibling is named explicitly, so the differentiation rests on inference rather than a direct statement.

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?

The opening sentence gives a clear trigger condition ('already owns a domain at another provider'), and the closing sentence covers the in-tool branch for palimpalem-managed domains. What is missing is explicit routing against alternatives (e.g. what to use when the domain is not yet owned, or when the person only wants to inspect DNS records).

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.