Skip to main content
Glama
Systems Manager

Systems Manager

Disable Windows Features

sm_system_disable_windows_features
Destructive

Disable specified Windows features to control system capabilities and reduce unnecessary enabled components.

Instructions

Disable 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_disable_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.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say what disabling a feature affects, whether a reboot is needed, whether the change is reversible, or what privileges are required. The generic 'managing packages, system health, and updates' sentence is boilerplate that does not describe this action.

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?

Only two sentences and the action is front-loaded, but the second sentence is category boilerplate that does not earn its place and dilutes the definition rather than sharpening it.

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?

For a destructive, non-idempotent system mutation with no output schema, the description should at minimum mention consequences, reversibility, and privilege requirements. The fully described two-parameter schema covers inputs, but the agent still lacks the operational context needed to invoke a destructive tool confidently.

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% – both the confirm flag and feature_name are documented in the schema itself. The description contributes no extra meaning, such as accepted feature-name format or expected behavior when confirm is false, so the baseline 3 applies.

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 opens with a specific verb+resource phrase, 'Disable windows features', which an agent can immediately distinguish from the sibling sm_system_enable_windows_features and sm_system_list_windows_features. The trailing parenthetical and category blurb add no precision, but the core action is unambiguous.

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 alternatives such as sm_system_enable_windows_features or the service-disable siblings, and no stated preconditions (admin rights, target machine, reboot requirement). The agent is left to infer the entire usage context from the name.

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