Skip to main content
Glama

Remove host

tunnel_manager_remove_host
Destructive

Remove a host from the managed host inventory using its alias. Set confirm=true to authorize the destructive deletion when no confirmation prompt is available.

Instructions

Invoke the remove_host operation.

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": {
      "alias": "<alias>"
    },
    "name": "tunnel_manager_remove_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasYes
confirmNoExplicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.4.7
    • addedInput schema / properties / confirm
      Added value: +{
      +  "default": false,
      +  "description": "Explicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.",
      +  "type": "boolean"
      +}
  2. Addedv3.3.1

TDQS

D1.5/5.0
Behavior1/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds nothing beyond that — it does not say what gets destroyed, whether the host entry is recoverable, whether an inventory save/reload is required afterwards, or what happens on failure. For a destructive operation the description carries no behavioral weight at all.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The single sentence is short but vacuous — brevity here reflects under-specification rather than efficient communication. There is no front-loaded statement of what is removed or what the agent should expect.

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

Completeness1/5

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

A destructive, open-world mutation with no output schema and half its parameters undocumented needs far more description than one clause. Nothing tells the agent how to verify success, whether the removal persists to the inventory, or how alias resolution works.

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 `confirm` parameter has a decent inline schema description, but `alias` is undocumented (50% coverage) and the tool description does not explain what an alias refers to, how to obtain one, or whether it must match a previously added/loaded host. No meaning is added beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Invoke the remove_host operation" restates the tool name without stating the resource being acted on, any scope, or what removal entails. An agent learns nothing it could not infer from the name `tunnel_manager_remove_host` alone, and there is no differentiation from sibling delete-flavored tools such as `tm_remote_remove_host_key`.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, no prerequisites, no exclusions, and no mention of alternatives among the ~35 siblings (e.g. `tm_remote_remove_host_key` for keys vs. this for tunnel hosts). The agent must guess entirely from the name.

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