Control Plane

Update a Domain

update_domain

DestructiveIdempotent

Update metadata (description, tags), top-level spec flags (acceptAllHosts, acceptAllSubdomains), or the GVC/workload binding. Ports, routes, TLS, and CORS have their own tools (add/update/remove_domain_route, add/remove_domain_port, set/clear_domain_tls; CORS in the full profile). After binding gvcLink/workloadLink, re-read status.dnsConfig — bindings add records the user must create.

Input Schema

TableJSON Schema

Name	Required	Description
`org`	No	Organization slug.
`tags`	No	Add or update tags without replacing the full set. Submit an empty list to clear all tags.
`domain`	Yes	Fully qualified domain name to update.
`gvcLink`	No	Bind the domain to a GVC (e.g., /org/{org}/gvc/{gvc} or //gvc/{gvc}). Mutually exclusive with `removeGvcLink` and `workloadLink`.
`description`	No	New description for the domain.
`workloadLink`	No	Bind the entire domain to one workload (e.g. //gvc/{gvc}/workload/{name}). Mutually exclusive with `removeWorkloadLink` and `gvcLink`.
`removeGvcLink`	No	Detach the domain from its current GVC binding.
`removeTagKeys`	No	Tag keys to remove from the resource.
`acceptAllHosts`	No	Accept any host header (overrides existing).
`removeWorkloadLink`	No	Detach the domain from its current workload binding.
`acceptAllSubdomains`	No	Accept any subdomain (overrides existing).

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`data`	No	The full result. Read this, not only the summary.
`details`	No
`summary`	Yes
`nextSteps`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedSep 30, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / description / maxLength
```
Removed value: -250
```
- removedInput schema / properties / domain / maxLength
```
Removed value: -253
```
- removedInput schema / properties / domain / minLength
```
Removed value: -1
```
- removedInput schema / properties / gvcLink / minLength
```
Removed value: -1
```
- changedInput schema / properties / org / description
```
Previous value: -"Organization slug (lowercase kebab-case). NEVER guess — if the user has not named one, ask. On org-not-found, stop and ask; do not retry variants."New value: +"Organization slug."
```
- removedInput schema / properties / org / maxLength
```
Removed value: -63
```
- removedInput schema / properties / org / minLength
```
Removed value: -1
```
- removedInput schema / properties / org / pattern
```
Removed value: -"^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"
```
- removedInput schema / properties / removeTagKeys / items / minLength
```
Removed value: -1
```
- removedInput schema / properties / tags / items / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / tags / items / properties / key / minLength
```
Removed value: -1
```
- removedInput schema / properties / tags / maxItems
```
Removed value: -50
```
- removedInput schema / properties / workloadLink / minLength
```
Removed value: -1
```
- changedInput schema / required
```
Previous value: -[
-  "org",
-  "domain"
-]New value: +[
+  "domain"
+]
```
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedOutput schema / additionalProperties
```
Removed value: -false
```
- changedOutput schema / properties / data / description
```
Previous value: -"The full machine-readable result — list rows, the resource object, query results. Read THIS, not just the summary."New value: +"The full result. Read this, not only the summary."
```
- addedOutput schema / properties / details
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / nextSteps / description
```
Removed value: -"Recommended follow-up actions for this task, in order."
```
- removedOutput schema / properties / ok / description
```
Removed value: -"Whether the call succeeded."
```
- removedOutput schema / properties / summary / description
```
Removed value: -"One-line summary of the result."
```
First observedJun 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare the mutation profile (destructiveHint=true, idempotentHint=true, openWorldHint=true), so the safety bar is lower. The description adds genuinely non-obvious behavior: binding gvcLink/workloadLink creates DNS records the user must provision, so status.dnsConfig should be re-read. It doesn't add permission/rate-limit details, but the DNS side-effect disclosure is valuable context beyond annotations.

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?

Front-loads what the tool updates, then the boundary against sibling tools, then the DNS caveat. Dense, no filler, every sentence carries new information.

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?

With an output schema present, return values need not be explained, and the description covers scope, sibling boundaries, and the DNS-record side effect. It omits permission requirements for a destructive+open-world mutation, which is a minor remaining gap.

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 of the 11 params is self-documented, including mutual-exclusivity notes (gvcLink vs removeGvcLink/workloadLink), so the baseline is 3. The description groups the params into functional clusters (metadata / spec flags / binding), which adds a mild mental model but no syntax or format detail beyond the schema.

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+resource and precisely enumerates what can be updated (metadata, spec flags, GVC/workload binding). It explicitly names the mutation areas that belong to sibling tools (routes, ports, TLS, CORS), so an agent can distinguish it from update_domain_route, add_domain_port, set_domain_tls without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to the correct alternatives by name: add/update/remove_domain_route, add/remove_domain_port, set/clear_domain_tls, and notes CORS lives in the full profile. This is clear when-to-use/when-not-to-use guidance tied to concrete sibling tools.

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

All Control Plane tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.