Skip to main content
Glama
sandraschi

Windows Operations MCP

by sandraschi

winops_process_list

Read-onlyIdempotent

List running Windows processes with CPU and memory usage, optionally filtering by name and including system processes.

Instructions

List running Windows processes with CPU and memory usage.

Return Format

{
  "success": true,
  "processes": [{"pid": int, "name": str, "user": str, "cpu": float, "mem": float}],
  "count": int,
  "has_more": bool
}

Examples

list(name_filter="python", limit=20)
list(include_system=True, limit=100)

Notes:

  • Result is bounded by limit. If count == limit, has_more may be true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax processes to return (1-500).
name_filterNoSubstring filter on process name.
include_systemNoInclude SYSTEM/LOCAL SERVICE processes.
Behavior4/5

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

Annotations already declare this read-only and idempotent, and the description adds useful behavior not visible there: exact return shape, limit bounds, and the has_more flag. This is a helpful addition, though no mention is made of permission or edge cases around SYSTEM processes beyond the schema.

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?

The description is well-structured with a format block, examples, and a short note. It is concise, readable, and each section adds value without unnecessary repetition.

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

Completeness5/5

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

There is no output schema, but the description provides a structured return format and explains pagination-like behavior with `count == limit` and `has_more`. This is complete enough for an agent to understand what will be returned and what constraints apply.

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?

All three parameters are fully described in the input schema, so the baseline of 3 applies. The description reinforces the parameters with examples and explains the limit/has_more relationship, but it does not add substantially new parameter semantics beyond what the schema already says.

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 clearly states the action ('List running Windows processes') and the resource scope (CPU and memory usage). It does not explicitly differentiate from sibling tools like process_list_card or process_resources, but the verb+resource 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The examples provide clear usage patterns with name_filter and include_system, and the note about limit/has_more sets expectations. However, it does not explain when to choose this over process_list_card or process_info, so alternatives are not explicitly covered.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/windows-operations-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server