Skip to main content
Glama

winrm_host_list

Read-only

List saved WinRM hosts with passwords redacted, and filter results by tag or scope to target the right machines before running remote PowerShell or CMD commands.

Instructions

List saved WinRM hosts with passwords redacted; optionally only hosts carrying a tag.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "winrm_host_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
scopeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tag
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Tag"
      +}
  2. First observedv0.2.2

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description adds a genuinely useful behavioral fact — returned records have passwords redacted — but says nothing about ordering, pagination, or what an empty inventory looks like, and an output schema is present so return-shape detail is not required.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; the core operation comes first and the optional filter follows after the semicolon.

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?

With a read-only annotation profile and an output schema, the description needs mainly to cover the two inputs and the filtering behavior. The redaction note is a valuable addition, but the undocumented scope parameter leaves a real hole for a tool an agent may call without arguments or with an ambiguous scope string.

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%, so the description must carry both parameters. It explains tag (filter to hosts carrying that tag) but leaves scope entirely undefined, meaning half the parameters have no semantic guidance anywhere.

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 gives a specific verb and resource ("List saved WinRM hosts") plus a scope qualifier ("passwords redacted"), which is enough to separate it from winrm_host_get and the save/update/delete siblings. It stops short of naming an alternative explicitly, so it lands at clear-but-not-differentiating.

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?

"optionally only hosts carrying a tag" implies the filtering use case, so an agent can infer when to pass a tag. There is no explicit when-to-use versus winrm_host_get or winrm_inventory_status, and no statement about prerequisites such as an initialized inventory.

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