Skip to main content
Glama

Manage a project domain

manage_project_domain
DestructiveIdempotent

Connects, verifies, enables, redirects or removes a project hostname. Optional project subdomains use one child label under the saved hosting address and provision DNS and HTTPS automatically. External domains require ownership verification; static aliases share the same published files. Applications 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_project_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.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered. The description adds meaningful operational context beyond that: automatic DNS/HTTPS provisioning for subdomains, ownership verification for external domains, and shared files for static aliases. It still does not say what removal destroys or how redirects behave for existing traffic.

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?

The definition is four dense sentences and front-loads the action set before moving to domain-type rules. Every sentence contributes, though the phrasing is compressed enough that the parameter mapping is left implicit.

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

Completeness3/5

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

This is a destructive, open-world mutation tool with no output schema and low parameter coverage. The description covers domain types and provisioning behavior, but with seven parameters it should also explain the required idempotency key usage and what a removal or redirect does to existing DNS/HTTPS.

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%, so the description must carry weight for the seven parameters. It indirectly maps the verbs to the boolean controls (verify, active/enable, remove, redirect_to) and explains subdomain versus external hostname behavior, but it does not define hostname format, redirect_to semantics, or the interaction between active and remove.

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 uses specific verbs (connects, verifies, enables, redirects, removes) against a concrete resource (a project hostname), so an agent can tell what the tool does. It does not distinguish this tool from the sibling manage_dynamic_domain, so differentiation is missing.

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 through the subdomain-vs-external-domain distinction and the ownership verification requirement for external domains. There is no explicit guidance on when to choose this tool over manage_dynamic_domain or other domain-related siblings.

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