Skip to main content
Glama

add_host

Add an SSH host to a personal vault or team so agents can connect through Detour using saved credentials, requesting vault edit access first if needed.

Instructions

Add a host to the person's vault, or to a team (needs vault:edit; in a team, over all its hosts). To use it, request access to it.

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": {
      "name": "<name>",
      "address": "<address>"
    },
    "name": "add_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoLog in with this key of the vault (its name). Without it, ssh-agent is used.
nameYesA name for the host.
portNoSSH port (default 22).
teamNoThe team to add it to (its name); the personal vault if not given.
userNoThe user to log in as (default root).
groupNoThe group in the host list.
proxyNoReach it through this saved proxy of the vault (its name).
addressYesIts address: a name or an IP.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the required permission scope and clarifies that team access applies across all of that team's hosts, which is genuinely useful. It omits mutation side effects such as behavior on duplicate names, error semantics, and whether the new host is immediately usable.

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?

Two short sentences with the purpose front-loaded and the permission note trailing. The phrase "To use it, request access to it" is slightly circular and vague about the mechanism, but nothing is bloated.

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 an 8-parameter creation tool with no annotations and no output schema, the description covers purpose, permission scope, and an access workflow. It leaves gaps on duplicate handling, confirmation of what gets created, and failure modes, which matter for a write operation with this many optional fields.

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 one of the 8 parameters (key, port, user, group, proxy, team, etc.) is already documented in the schema. The description adds only the vault-vs-team framing, not any per-parameter meaning, 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 and resource ("Add a host") and states the two destinations: the person's vault or a team. It is clearly distinct from remove_host/update_host by virtue of the 'add' action, though it does not explicitly contrast with them.

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

Usage Guidelines3/5

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

It gives a real prerequisite (needs vault:edit) and an onboarding step ("request access to it"), which tells the agent what must be true before calling. It offers no explicit when-not guidance and no named alternative for cases where the host already exists (e.g., update_host).

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