Skip to main content
Glama

create-redirection-host

create-redirection-host

Creates a redirection host that forwards matched domains to a target URL using a configurable HTTP status code.

Instructions

Create a new redirection host. Forwards matched domains to a target URL with configurable HTTP status code.

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": {
      "instanceName": "<instanceName>",
      "domainNames": "<domainNames>",
      "forwardScheme": "<forwardScheme>",
      "forwardHttpCode": "<forwardHttpCode>",
      "forwardDomainName": "<forwardDomainName>"
    },
    "name": "create-redirection-host"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNo
sslForcedNo
domainNamesYesList of domain names to redirect
hstsEnabledNo
http2SupportNo
instanceNameYes
preservePathNo
blockExploitsNo
certificateIdNo
forwardSchemeYes
advancedConfigNo
hstsSubdomainsNo
forwardHttpCodeYes
forwardDomainNameYesTarget domain to forward to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It explains the redirect concept and that the status code is configurable, but says nothing about permissions, whether the host is enabled immediately, side effects on DNS/certificates, or what is returned after creation.

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?

Two tight sentences with the action front-loaded and the resource's behavior immediately after; nothing is wasted. It is perhaps too terse given the tool's complexity, but it is structurally sound.

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?

The description is complete enough to identify the operation, and no output schema exists so return values need not be explained. However, for a 14-parameter mutation with no annotations and near-zero schema coverage, far more behavioral and parameter context is required for confident invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14% across 14 parameters (domainNames and forwardDomainName are the only documented ones), so the description must compensate and does not. Beyond hinting that an HTTP status code is configurable, it adds no meaning for forwardScheme, preservePath, sslForced, certificateId, instanceName, or the HSTS options.

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 ("Create a new redirection host") and explains what the created resource actually does: forwarding matched domains to a target URL with a configurable status code. That resource-level explanation distinguishes it from create-proxy-host without naming the sibling, though no explicit sibling comparison is made.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites (e.g. whether a certificate must exist first), and no mention of alternatives such as create-proxy-host for non-redirect traffic. An agent must infer applicability from the tool name alone.

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