Skip to main content
Glama

Configure a project hostname

manage_dynamic_domain
DestructiveIdempotent

Connects or changes an application hostname, alias or redirect. Optional project subdomains use one child label under the saved hosting address and provision DNS and HTTPS automatically. External custom domains require ownership verification. Aliases serve the same application, which can route by Host.

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": {
      "project_id": "<project_id>",
      "hostname": "<hostname>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "manage_dynamic_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
activeNo
removeNo
verifyNo
hostnameYes
project_idYesExact stable project ID. Resolve it first. Never invent an update target.
redirect_toNo
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a destructive, open-world, idempotent write; the description adds real context beyond them, namely that DNS and HTTPS are provisioned automatically and that external domains require ownership verification. However, it never says what the destructive path actually does (e.g., what happens when a hostname is removed, whether that action is reversible), which is the most important behavioral gap for a destructiveHint=true 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?

Three sentences, front-loaded with the action and then narrowing to subdomain vs custom-domain vs alias cases. Dense but every sentence carries information; no filler or restatement of the 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?

For a hostname-configuration tool with no output schema and low schema coverage, the description covers the important hostname-type distinctions and the verification prerequisite for external domains.

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 only 29% across 7 parameters, so the description must compensate and it partly does: it explains the hostname subdomain form ('one child label under the saved hosting address'), the external custom-domain case requiring verification, and the alias/redirect behavior. It says nothing about active, remove, or verify, which are the toggles an agent most needs to understand before calling a destructive tool.

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 opens with a specific verb and resource: 'Connects or changes an application hostname, alias or redirect,' and then distinguishes three hostname modes (project subdomain, external custom domain, alias). It is clear what the tool operates on, though it never names the sibling manage_project_domain to disambiguate domain configuration from project-level domain management.

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?

Usage context is implied rather than stated: external custom domains need ownership verification, subdomains use one child label under the saved hosting address. There is no explicit when-to-use/when-not guidance and no reference to the closely named sibling manage_project_domain, leaving the agent to infer which tool applies.

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