Skip to main content
Glama

winrm_inventory_status

Read-only

Check WinRM inventory status to see the project or user inventory path, whether it exists, and the saved host count.

Instructions

Show the project or user inventory path, existence, and saved host count.

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

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 the safety profile is covered. The description adds that it reports path, existence, and saved host count, but says nothing about what happens if the inventory does not exist or how project vs user inventories are resolved.

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 compact sentence with zero filler, front-loaded with the verb and the reported fields. Its brevity is appropriate, though it leaves the key `scope` parameter unexplained.

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 re-explained, and the tool is a simple single-optional-param read. Still, the undefined `scope` parameter and the absence of any usage context leave meaningful gaps for an agent deciding how to call it.

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 coverage is 0%: the single `scope` parameter has no description, no enum, and defaults to null. The phrase "project or user inventory" hints that `scope` may select between those, but the description never states the accepted values or the default behavior when omitted.

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 ("Show") and a specific set of reported facts (inventory path, existence, saved host count), which lets it be told apart from the sibling init/validate/host_* tools. It stops short of explicitly naming a sibling it is not, but the purpose is clear.

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 use this versus winrm_inventory_init, winrm_inventory_validate, or the host_* tools. The agent must infer that this is a read-only status check that precedes init/validate, with no explicit guidance or exclusions.

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