Skip to main content
Glama

Link domain to webspace

webspace_link_domain

Link a custom user-owned domain to a webspace. The Domain record must already exist and be owned by the user. Issues a Let's Encrypt certificate in the background; check webspace_get to see when sslActive becomes true.

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": {
      "id": "<id>",
      "domain": "<domain>",
      "domainId": "<domainId>",
      "dnsName": "<dnsName>"
    },
    "name": "webspace_link_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID
domainYesFull hostname to link (e.g. 'blog.example.com' or 'example.com')
dnsNameYesDNS record name (subdomain part, or '@' for the apex)
domainIdYesThe Domain record ID — must be owned by the authenticated user

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnly=false and destructive=false; the description adds real behavioral context beyond that — the ownership precondition and, importantly, that a Let's Encrypt certificate is issued asynchronously and must be verified via webspace_get (sslActive). It does not cover failure modes, duplicate links, or whether DNS must already point at the host, so not a 5.

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?

Two sentences, front-loaded with the action, then the precondition, then the async side effect and how to check it. No filler or redundant phrasing.

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?

For a 4-required-param mutation with no output schema, the description covers the key things an agent needs: prerequisite state, and the delayed certificate effect with a verification path. Minor gaps remain around failure behavior and whether DNS must pre-resolve, but nothing critical is missing.

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 coverage is 100% and each parameter already carries its own description (hostname format, '@' for apex, domainId ownership). The description adds essentially nothing about individual parameters beyond restating the ownership constraint, so the baseline 3 applies.

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 ('Link a custom user-owned domain to a webspace'), which is immediately distinguishable from the inverse sibling webspace_unlink_domain and from registration tools like register_domain. The scope (custom, user-owned) is explicit.

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?

Gives a clear precondition for use: 'The Domain record must already exist and be owned by the user,' which effectively routes the agent to register_domain/get_domain first if not. It does not explicitly name the alternative sibling or state when not to use it, so it falls short of a 5.

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.