Skip to main content
Glama

update-redirection-host

update-redirection-host

Modify an existing redirection host by updating only the fields you specify. Use this to change domains, SSL settings, or forwarding rules without affecting other configuration.

Instructions

Update an existing redirection host. Only provided fields are updated.

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>",
      "id": "<id>"
    },
    "name": "update-redirection-host"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
enabledNo
sslForcedNo
domainNamesNo
hstsEnabledNo
http2SupportNo
instanceNameYes
preservePathNo
blockExploitsNo
certificateIdNo
forwardSchemeNo
advancedConfigNo
hstsSubdomainsNo
forwardHttpCodeNo
forwardDomainNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses one useful trait: partial updates where only provided fields are changed. It says nothing about permissions, reversibility, side effects of changing domain or certificate fields, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded and free of filler. It is efficient, though for a 15-parameter mutation tool the brevity leaves structure gaps that belong under contextual completeness.

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

Completeness2/5

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

Given a 15-parameter mutation tool with no annotations, no output schema, and zero schema description coverage, the definition is substantially under-specified. Only the partial-update behavior is explained; most field meanings and operational constraints are absent.

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?

The schema has 15 parameters with 0% description coverage, so the description must compensate and largely fails to. The partial-update sentence clarifies optional-field behavior generically, but it does not explain domainNames, certificateId, forwardScheme, forwardHttpCode, or the other security-related booleans.

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 states a specific verb and resource: 'Update an existing redirection host.' An agent can distinguish this from proxy-host siblings by resource type, though it does not explicitly contrast with create/delete/enable/disable redirection-host tools.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as enable/disable or create. The phrase 'existing' implies the host must already exist, but the agent must infer that.

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