Skip to main content
Glama

Get HTTP forward

get_forward
Read-onlyIdempotent

Retrieve the HTTP forward configured for a specific host and domain ID. Use it to inspect where a subdomain or root host currently redirects visitors.

Instructions

Get the HTTP forward configured for a specific 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>"
    },
    "name": "get_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesthe host/subdomain the forward applies to, e.g. 'www' or '@' for the root
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. Changed1 schema field changedv2.0.0
    • addedInput schema / properties / host / minLength
      Added value: +1
  3. First observedv1.1.1

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is fully covered by structured fields. The description adds nothing beyond that: no error/empty-result behavior, no indication of what a configured forward returns, no note that the domain must exist. The lower bar from annotations keeps this from a 1, but the value added is minimal.

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?

A single front-loaded sentence with zero filler, stating the resource and its scope immediately.

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 simple two-parameter read tool with a full output schema and strong annotations, the description is nearly sufficient; the only meaningful gap is the not-found/empty-result behavior, which an agent calling get_forward would plausibly hit.

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%, with 'host' documented (including the '@' root convention) and 'domain_id' pointing at list_domains. The description only echoes 'specific host' and adds no meaning about domain_id or the host format beyond what the schema states, so the baseline 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?

The description names a specific verb ('Get') and a specific resource ('the HTTP forward configured for a specific host'), so an agent can distinguish it from the mutating siblings (create_forward, update_forward, delete_forward). It does not explicitly contrast with list_forwards, which is the closest sibling, but the singular 'for a specific host' implies the scoped lookup.

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 when-to-use guidance: nothing states that this retrieves a single existing forward rather than enumerating them, and no alternative (list_forwards) is named. It also omits what happens when no forward exists for the host, which is exactly the decision an agent needs to make before calling.

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