Skip to main content
Glama

update_host

Modify an existing SSH host's name, address, port, user, group, or proxy in a vault or team, requiring vault:edit permission and access to that host.

Instructions

Change a host of the person's vault or of 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": "update_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host to change.
nameNo
portNo
userNo
groupNo
proxyNoA saved proxy of the vault to go through (its name), or "none" for directly.
addressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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, and it does disclose the authorization requirement and an access-scope restriction, which are genuinely useful. It does not disclose the most consequential behavioral trait for a 6-optional-field mutation: whether omitted or null fields leave the existing host untouched or clear it, nor anything about reversibility or failure modes.

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?

A single front-loaded sentence with a parenthetical for constraints; every clause carries information. 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.

Completeness2/5

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

For a 7-parameter mutation tool with no annotations, no output schema, and low schema coverage, the definition is thin. The critical missing piece is update semantics — whether this is a merge or a full replace — which an agent cannot infer from the supplied fields.

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?

Schema description coverage is only 29%, with 7 parameters, so the description needs to compensate and does not. It never explains the semantics of the nullable name/port/user/group/address fields, the partial-update behavior, or the unusual "none" sentinel for proxy that the schema itself flags.

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?

"Change a host" gives a specific verb and resource, and the description narrows scope to hosts in the person's vault or a team's vault, which implicitly separates it from add_host/remove_host. It stops short of naming a sibling or stating what "change" covers, so it is clear but not maximally differentiated.

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?

The prerequisites are stated explicitly ("needs vault:edit"; in a team, only a host your access reaches), which tells the agent when the call will be permitted. However, there is no guidance on when to prefer this over add_host or remove_host, and no mention of what to do when a host does not yet exist.

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