Skip to main content
Glama

Delete HTTP forward

delete_forward
DestructiveIdempotent

Deletes an HTTP forward for a specified domain ID and host, permanently removing the redirect. Use it to stop forwarding traffic when a host no longer needs a redirect.

Instructions

Delete an HTTP forward. This cannot be undone.

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>"
    },
    "name": "delete_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesthe host/subdomain whose forward should be deleted
domain_idYesthe Domeneshop domain ID, from list_domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
  2. Changed1 schema field changedv2.0.0
    • addedInput schema / properties / host / minLength
      Added value: +1
  3. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The sentence 'This cannot be undone' restates the destructive nature in concrete terms but adds no new operational detail such as behavior when the forward does not exist or what the response contains. With annotations carrying the main burden, a 3 is warranted.

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 short sentences, no filler, with the action stated first and the irreversibility warning immediately after. Every word earns its place.

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?

This is a simple two-parameter destructive tool with fully annotated schema and no output schema, so little explanation is required. The description covers action and irreversibility; only the idempotent-not-found behavior is left implicit, which the annotation hints at.

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%: host is documented as 'the host/subdomain whose forward should be deleted' and domain_id points to list_domains. The description adds nothing beyond this, which is acceptable when the schema does the heavy lifting.

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 gives a specific verb ('Delete') and resource ('HTTP forward'), which is clearly distinct from create_forward, update_forward, or delete_dns_record. It does not explicitly name the sibling it differs from, but the resource noun is specific enough for an agent to route correctly.

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 guidance on when to choose this over alternatives such as update_forward (to change a target) or delete_dns_record (for DNS records rather than forwards). No preconditions, no note about what to do if the forward is missing. Usage must be fully inferred from the name.

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