Skip to main content
Glama

Create HTTP forward

create_forward

Create an HTTP forward for a domain host to a destination URL; use it when a host needs redirecting and no existing forward or conflicting DNS record exists.

Instructions

Create a new HTTP forward for a domain. Fails if the host already has a forward or a conflicting A, AAAA, ANAME or CNAME record.

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": "create_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/5.0
Behavior4/5

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

Annotations already cover the safety profile (not read-only, not destructive, not idempotent, open-world), so the bar is lower; the description adds genuine value by disclosing the conflict-check semantics that determine whether the call succeeds. It omits permission/auth requirements and whether the forward goes live immediately, which keeps it from a 5.

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?

Two sentences, both earning their place, with the core action front-loaded and the constraint following. Nothing redundant or padded.

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 four-parameter create tool with full schema coverage, an output schema, and annotations, the definition covers what an agent needs to attempt the call and anticipate failure. A note on prerequisites (domain ownership, propagation delay) or routing to update_forward would close the 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 description coverage is 100%, so every parameter including the frame default is already documented in the schema. The description adds no extra meaning about domain_id, host, url or frame, so the baseline of 3 applies.

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 HTTP forward for a domain'), which cleanly separates it from the update_forward/delete_forward siblings in the list. It does not explicitly name those siblings as alternatives, so it stops short of full differentiation.

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?

The description gives a concrete precondition for failure: the host must not already have a forward or a conflicting A, AAAA, ANAME or CNAME record. That is an effective when-not rule, though it never points the agent at update_forward for the modify case or states what to do when the conflict arises.

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