Skip to main content
Glama
Systems Manager

Systems Manager

List Windows Features

sm_system_list_windows_features
Read-onlyIdempotent

Lists Windows features on a managed system to help you check availability and verify installed capabilities before enabling or troubleshooting them.

Instructions

List windows features (sm_system_operations). System operations for managing packages, system health, and updates

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": "sm_system_list_windows_features"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

B3/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds no additional behavior detail: no indication of what a 'feature' looks like, whether results are paginated, or whether elevated privileges are needed to enumerate features. The generic second sentence ('System operations for managing packages, system health, and updates') describes the whole tool family, not this tool.

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

Conciseness3/5

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

The first clause is front-loaded and efficient. The rest is filler: the '(sm_system_operations)' parenthetical and the family-level sentence about packages, system health and updates add no information about this specific tool and dilute the signal.

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?

This is a simple zero-parameter read tool with a full set of annotations and no output schema. The description names the operation but does not say what the returned feature list contains (names only? install state? both?), which is the main thing an agent cannot learn from structured fields. It is minimally adequate, not complete.

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

Parameters4/5

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

The tool takes no parameters, so there is nothing parameter-level for the description to clarify. The baseline of 4 applies: with an empty schema, the description need not compensate for anything.

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+resource: 'List windows features'. The scope is unambiguous for a zero-parameter tool. It does not distinguish itself from siblings such as sm_system_enable_windows_features or sm_system_disable_windows_features, and the trailing parenthetical plus 'System operations for managing packages, system health, and updates' is generic category text rather than a differentiator.

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 explicit when-to-use guidance, no mention of when not to use it, and no pointer to alternatives. An agent must infer that this is the read counterpart of the enable/disable siblings. Nothing in the text tells the agent which one to pick.

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

Deploy Server

Other Tools