Skip to main content
Glama
Systems Manager

Systems Manager

Enable Windows Features

sm_system_enable_windows_features
Destructive

Enable Windows features on managed hosts to install required system capabilities and resolve missing component issues.

Instructions

Enable 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_enable_windows_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.
feature_nameNoWindows feature name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of required administrator privileges, whether a reboot follows, whether existing state is recoverable, or what happens on an invalid feature name.

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 definition is short and front-loads the verb and resource, which is good. The second sentence, however, is generic category filler that does not apply specifically to enabling Windows features and wastes the only space available for useful detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive system-mutating tool with no annotations gap, the description omits privilege requirements, reboot implications, and failure modes. While the schema and annotations cover parameters and safety, the behavioral context is still thin.

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

Parameters3/5

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

Schema description coverage is 100%, with both confirm and feature_name documented inline, so the baseline is 3. The description contributes no additional meaning about parameter usage, such as where a valid feature_name must come from.

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: 'Enable windows features', which is immediately identifiable. However, it does not distinguish this tool from the sibling sm_system_disable_windows_features or sm_system_list_windows_features, and the trailing clause about 'packages, system health, and updates' describes a broader category rather than this tool's actual scope.

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 guidance on when to use this tool versus the disable or list variants, and no stated preconditions. An agent must infer from the name alone that this is the inverse of the disable sibling.

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