Skip to main content
Glama

Update HTTP forward

update_forward
DestructiveIdempotent

Change the destination URL or frame setting for an existing HTTP forward on a Domeneshop domain using its domain ID and host; to change the host, delete and recreate the forward.

Instructions

Update an existing HTTP forward for a domain. Returns the stored forward. frame keeps its stored value unless given. The host itself cannot be changed: to move a forward, delete it and create it again for the new host.

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": {
      "domain_id": "<domain_id>",
      "host": "<host>",
      "url": "<url>"
    },
    "name": "update_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesthe destination URL to forward requests to, including the scheme: http://, https:// or ftp://
hostYesthe host/subdomain to forward, e.g. 'www' or '@' for the root
frameNoif true, show the destination in a frame instead of redirecting; defaults to false for a new forward and to the stored value when updating
domain_idYesthe Domeneshop domain ID, from list_domains

Output Schema

NameRequiredDescriptionDefault
urlYes
hostYes
frameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.7
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed4 schema fields changedv2.0.0
    • changedInput schema / properties / frame / description
      Previous value: -"if true, show the destination in a frame instead of redirecting; defaults to false"New value: +"if true, show the destination in a frame instead of redirecting; defaults to false for a new forward and to the stored value when updating"
    • addedInput schema / properties / host / minLength
      Added value: +1
    • changedInput schema / properties / url / description
      Previous value: -"the destination URL to forward requests to, starting with http:// or https://"New value: +"the destination URL to forward requests to, including the scheme: http://, https:// or ftp://"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "frame": {
      +      "type": "boolean"
      +    },
      +    "host": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "host",
      +    "url"
      +  ],
      +  "type": "object"
      +}
  3. First observedv1.1.1

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 (readOnly=false, destructive=true, idempotent=true, openWorld=true), so the description only needs to add context. It does: partial-update semantics for 'frame keeps its stored value unless given', the immutability of the host, and the fact that the stored forward is returned. It never explains what 'destructive' means here (e.g. that the previous url is overwritten), which is the one gap.

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 short sentences, front-loaded with purpose and return value, then the carry-over rule, then the immutability constraint with its workaround. No filler or restatement of the title.

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?

An output schema exists so return shape needs no explanation, and annotations carry the risk profile. The description covers immutability, field carry-over and the delete/recreate workaround. Slightly incomplete in not saying whether omitted non-frame fields (e.g. url, which is required) are reset, though required-ness in the schema mitigates this.

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?

Schema coverage is 100%, so 3 is the baseline. The description still earns above baseline by clarifying the required 'host' parameter is effectively an identifier rather than something editable, and by restating the frame carry-over rule that an agent might otherwise miss when composing a full-replace update.

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 ('Update an existing HTTP forward for a domain'), scopes it with 'existing', and immediately discloses the return value. This is plainly distinguishable from create_forward, delete_forward and update_dyndns without opening a schema.

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

Usage Guidelines4/5

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

Gives one explicit when-not/alternative path: the host cannot be changed, so moving a forward requires delete_forward plus create_forward on the new host. It does not state broader when-to-use conditions versus patch/upsert-style siblings, but the key migration case is routed.

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