Skip to main content
Glama

winrm_inventory_validate

Read-only

Validate a WinRM inventory file and check every saved host to catch configuration or connectivity issues before running commands.

Instructions

Validate an inventory file and every saved WinRM host.

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_inventory_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3/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 and locality are covered. The description usefully adds that validation spans both the inventory file and all saved hosts, which is real scope information beyond the annotations, but it never says what an invalid result looks like or whether validation mutates/normalizes the file.

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?

One front-loaded sentence with no filler; the operation and its targets land immediately. It is arguably too terse for the amount of information an agent actually needs, but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. Still, for a validation tool the description omits what is validated, what constitutes failure, and what "scope" controls, leaving meaningful gaps against the tool's complexity.

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?

The single optional parameter "scope" has 0% schema description coverage and the description never mentions it, so its meaning (which hosts or which file subset is validated) is undocumented in both places. With no parameter count of zero to justify a free baseline, this is a clear gap.

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 ("validate") and its two objects (the inventory file and every saved WinRM host), so an agent knows exactly what operation runs. It does not, however, distinguish itself from nearby siblings such as winrm_inventory_status or winrm_test, leaving the 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 Guidelines2/5

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

There is no statement of when to validate versus when to check status or run winrm_test, and no prerequisites or exclusions are given. The agent must infer the usage context from the tool name alone.

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