Skip to main content
Glama

winrm_host_update

Idempotent

Update selected settings on a saved Windows host and remove optional values by field name. Use it to modify existing host inventory entries without recreating them.

Instructions

Update selected settings on a saved host; remove optional values with remove_fields.

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>",
      "changes": "<changes>"
    },
    "name": "winrm_host_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
scopeNo
changesYes
remove_fieldsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare idempotent=true, destructiveHint=false, and readOnly=false, so the safety profile is covered. The description adds one behavioral trait the annotations do not: that field removal is a separate, explicit operation via remove_fields rather than implicit through `changes`. It still does not say whether `changes` merges into or replaces existing settings, nor what errors occur for an unknown host name.

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 the mutation stated first and the removal escape hatch second; no filler or restatement of the tool name. It is tightly written, though the terseness contributes to the coverage gaps elsewhere rather than being optimal sizing for a four-parameter nested tool.

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?

An output schema exists, so return values need not be described, but the input side is far too thin: a nested free-form `changes` object, an untyped `scope`, and 0% schema coverage mean the agent cannot construct a valid call from the definition alone. Missing are the accepted change keys, merge-vs-replace semantics, and the meaning of scope.

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 0% across four parameters, and `changes` is a free-form object with additionalProperties: true — the highest-risk shape possible with no documentation. The description only clarifies remove_fields (partially, as a list of field names), leaving `name`, `scope` (a nullable, untyped-purpose field), and every acceptable key in `changes` completely unexplained in both schema and description.

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?

"Update selected settings on a saved host" gives a specific verb (update), a target (settings), and a precondition (host is already saved), which implicitly separates it from winrm_host_save and winrm_host_get. It never names a sibling explicitly and leaves "selected settings" unenumerated, so an agent still has to guess whether it overlaps with winrm_host_save.

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 clause "remove optional values with remove_fields" is real usage guidance for one parameter, and "saved host" implies the host must already exist. There is no explicit when-to-use vs winrm_host_save, no when-not, and no alternatives listed, so routing between the two write-path tools is left to inference.

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