Skip to main content
Glama

add_domain

Configure a service to serve on a domain with automatic HTTPS, including wildcard hosts and path-prefix routing so multiple services can share one host.

Instructions

Serve a service on a domain with automatic HTTPS. The host may be a wildcard (*.example.com); several services, even in other projects, can share a host on different path prefixes, and the longest prefix wins.

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": {
      "service": "<service>",
      "host": "<host>",
      "port": "<port>"
    },
    "name": "add_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesexample.com or *.example.com
pathNoPath prefix, default /
portYesContainer port
httpsNo
serviceYesService id or `project.service`, e.g. `shop.api`
via_tunnelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.36
    • changedInput schema / properties / host / description
      Previous value: -"example.com"New value: +"example.com or *.example.com"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With zero annotations, the description does the behavioral work itself: it discloses automatic HTTPS provisioning, wildcard host support, and cross-project host sharing with longest-prefix-wins resolution. It is silent on key operational traits such as what happens on a duplicate host+path collision, whether certificate issuance is synchronous, permission requirements, or what the response contains.

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 primary action and followed by the routing rule an agent most needs. Every clause — wildcard, cross-project sharing, longest prefix wins — carries operational weight with no filler.

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?

For a 6-parameter mutation tool with no annotations, no output schema, and only 67% schema coverage, the description covers host/path resolution well but omits the meaning of https and via_tunnel and says nothing about collision behavior. Adequate to invoke correctly in the common case, but not complete.

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?

Beyond the schema, the description explains that host accepts a wildcard, that path prefixes let multiple services (even cross-project) share one host, and that the longest prefix wins — genuine routing semantics the schema's bare 'Path prefix, default /' does not convey. It still leaves https, via_tunnel, and port undiscussed, but the added meaning beyond the schema is substantive.

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?

States a specific verb and resource: 'Serve a service on a domain with automatic HTTPS,' which tells an agent exactly what the call accomplishes and clearly implies the inverse of the sibling remove_domain. It stops short of explicitly naming that sibling or any alternative for a different kind of routing setup.

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: the note that several services can share a host on different path prefixes implies when to reuse a host instead of picking a new one. There is no explicit when-to-use/when-not-to-use guidance, no prerequisite information, and no pointer to remove_domain or update_service for follow-up operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.