Control Plane

Add a Domain Port Listener

add_domain_port

Idempotent

Add a new port listener to a domain. Minimal port is {number, protocol}; routes, cors, and tls are optional. Errors if a listener for that port number already exists — use the route/CORS/TLS tools to modify an existing listener instead.

Input Schema

TableJSON Schema

Name	Required	Description
`org`	No	Organization slug.
`port`	Yes	Complete port listener definition. Minimal valid listener: { "number": 443, "protocol": "http" }; routes, cors, and tls are optional.
`domain`	Yes	Fully qualified domain name.

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.

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / port / properties / routes / items / properties / caseInsensitive

Added value: +{
+  "description": "Optional. When true, prefix matches the path regardless of case. Prefix only; for a case-insensitive regex start it with (?i).",
+  "type": "boolean"
+}

Changed33 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 / domain / 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 / port / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / port / properties / cors / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / port / properties / cors / properties / allowOrigins / items / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / port / properties / cors / properties / maxAge / pattern
```
Removed value: -"^[\\d\\.]+[hms]+$"
```
- removedInput schema / properties / port / properties / routes / items / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / port / properties / routes / items / properties / headers / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / port / properties / routes / items / properties / headers / properties / request / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / port / properties / routes / items / properties / hostPrefix / pattern
```
Removed value: -"^[0-9a-zA-Z-\\._]*$"
```
- removedInput schema / properties / port / properties / routes / items / properties / mirror / items / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / port / properties / routes / items / properties / mirror / items / properties / workloadLink / minLength
```
Removed value: -1
```
- removedInput schema / properties / port / properties / routes / items / properties / prefix / pattern
```
Removed value: -"^\\/[0-9a-zA-Z-\\._~\\/]*$"
```
- removedInput schema / properties / port / properties / routes / items / properties / replacePrefix / pattern
```
Removed value: -"^\\/[0-9a-zA-Z-\\._~\\/]*$"
```
- removedInput schema / properties / port / properties / routes / items / properties / workloadLink / minLength
```
Removed value: -1
```
- removedInput schema / properties / port / properties / tls / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / port / properties / tls / properties / clientCertificate / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / port / properties / tls / properties / clientCertificate / properties / secretLink / minLength
```
Removed value: -1
```
- removedInput schema / properties / port / properties / tls / properties / serverCertificate / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / port / properties / tls / properties / serverCertificate / properties / secretLink / minLength
```
Removed value: -1
```
- changedInput schema / required
```
Previous value: -[
-  "org",
-  "domain",
-  "port"
-]New value: +[
+  "domain",
+  "port"
+]
```
- 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 declare openWorldHint=true and idempotentHint=true, so safety is covered, but the description adds the meaningful behavioral trait that duplicate port numbers fail and must be modified via other tools. It does not describe rate limits, auth requirements, or what the return payload contains, though an output schema exists.

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?

Three sentences, front-loaded with the action, then the minimal shape, then the error/alternative routing. No filler, and the most important constraint (duplicate error) is positioned where it will be read.

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 3-param tool with a very rich nested schema, complete schema coverage, an output schema, and annotations, the description needs only to add behavioral context and sibling routing, which it does. It stops short of mentioning the domain-warning status for non-443/80 ports that the schema notes, so it is not exhaustive.

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 100% and nested objects are fully documented by the schema itself, so the baseline is 3. The description's summary of the minimal port shape is accurate but adds no information 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 and resource ('Add a new port listener to a domain') and names the sibling tools (route/CORS/TLS) that handle modification. An agent can distinguish it from add_domain_route and set_domain_tls without opening their 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 states the minimal required fields, which fields are optional, and the error condition (listener already exists), then routes to the correct alternatives for modification. This is exactly the when-to-use/when-not-to-use guidance the dimension rewards.

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.