Skip to main content
Glama

winrm_test

Read-only

Verifies a WinRM connection by running a harmless PowerShell marker command and reports whether the account has local administrator rights.

Instructions

Test a WinRM connection with a harmless PowerShell marker command; reports whether the account is a local administrator.

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

Input Schema

NameRequiredDescriptionDefault
timeoutNo
connectionNo
saved_hostNo
inventory_scopeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds real value by disclosing that a PowerShell marker command is actually executed remotely and that the response reveals local-administrator membership. It stops short of noting credential/permission requirements or that a failed test surfaces as an error rather than a flag.

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?

One compact sentence with the action, mechanism, and result front-loaded; nothing is wasted or repeated.

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?

The output schema and annotations cover return values and safety, but the definition leaves the single most important decision — how to point the tool at a target — entirely undocumented across three overlapping parameters. For a 4-parameter tool with 0% schema coverage, that is a substantial omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters (timeout, connection, saved_host, inventory_scope) and the description says nothing about any of them. Critically, the agent gets no guidance on how to specify the target host — a bare connection object, a saved_host reference, or an inventory_scope — which are mutually exclusive-looking options with no explanation.

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 states a specific verb and resource ("Test a WinRM connection") and adds the mechanism ("harmless PowerShell marker command") plus the reported outcome (local administrator status). This clearly separates it from the winrm_execute_* siblings, though it never names an alternative explicitly.

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?

Usage is only implied: an agent can infer this is a pre-flight connectivity/permission check before running real commands. There is no statement about when to prefer it over winrm_inventory_validate or winrm_host_get, and no prerequisites or exclusions are given.

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