Skip to main content
Glama

remove_host

Removes a host from your vault or a team where your access reaches it. Use it to clean up SSH hosts you no longer need and keep your host list current.

Instructions

Remove a host from the person's vault or from a team (needs vault:edit; in a team, a host your access reaches).

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": {
      "host": "<host>"
    },
    "name": "remove_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's name, as list_hosts shows it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full load and does add real context: the required scope (vault:edit) and the access-reach constraint for team hosts. However, it is silent on whether removal is reversible, whether it kills active sessions to that host, or what happens to a team host outside the caller's reach -- meaningful gaps for a destructive operation.

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

Conciseness4/5

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

One tightly packed sentence with the action front-loaded and constraints in a parenthetical, so a reader gets the essential facts immediately. The nested parenthetical is slightly dense but nothing is wasted.

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

Completeness3/5

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

For a single-parameter destructive tool with no annotations and no output schema, the description covers permissions and scope, which is the core. It still lacks the consequences of the operation (reversibility, effect on sessions or access grants), which an agent would want before invoking a removal.

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?

Only one parameter, already fully documented in the schema ('The host's name, as list_hosts shows it'), so the schema does the heavy lifting. The description contributes the vault-vs-team scope of the 'host' argument but adds no format or disambiguation detail beyond that.

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?

Uses a specific verb-plus-resource phrase ('Remove a host') and scopes it to two containers ('the person's vault or from a team'), which is enough to distinguish it from remove_snippet, remove_tunnel, and remove_host's sibling 'remove'. It stops short of naming an alternative explicitly, so it is clear but not maximally differentiating.

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 the key precondition for invocation -- 'needs vault:edit' -- and a scoping rule for team hosts ('a host your access reaches'), which tells an agent whether it can call the tool at all. It does not state when to prefer a different removal tool or what to do when the permission is absent, so no alternatives are offered.

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