Skip to main content
Glama

winrm_host_save

Idempotent

Save a WinRM host to the project or user inventory with connection settings, optional environment-based password, and tags that group hosts for multi-host command execution.

Instructions

Save a WinRM host in the project or user inventory. Prefer password_env over password; tags (a list of strings) group hosts for winrm_execute_many.

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>",
      "settings": "<settings>"
    },
    "name": "winrm_host_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
scopeNo
settingsYes
overwriteNo

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 non-read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful context – the password_env security preference and the tags/winrm_execute_many linkage – but leaves the overwrite flag's effect on existing hosts and the scope target-resolution rules unexplained.

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, front-loaded with the operation and immediately followed by actionable configuration advice. No wasted wording, though the terseness contributes to the documentation gaps elsewhere.

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 mutating persistence tool with a fully undocumented nested settings object, an ambiguous overwrite flag, and an undefined scope parameter, the description is too thin. The presence of an output schema removes the need to document return values, but the input-side behavior remains substantially unexplained.

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 4 parameters including a free-form nested 'settings' object, so the schema supplies no meaning at all. The description only touches password_env and tags, both of which are keys inside settings rather than top-level parameters, and says nothing about name, scope semantics (project vs user inventory), or overwrite behavior.

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?

States a specific verb and resource: 'Save a WinRM host in the project or user inventory.' This clearly distinguishes a persistence operation from read siblings like winrm_host_get/winrm_host_list. It does not, however, differentiate 'save' from the sibling winrm_host_update, leaving the create-vs-update boundary implicit.

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?

Gives two concrete usage hints – prefer password_env over password, and use tags to group hosts for winrm_execute_many – which imply the tool's role in the workflow. But it never says when to use this versus winrm_host_update, nor when to set overwrite=true, so the main selection decision 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.