Windows Developer MCP Server

Overview Schema Source Related Servers Discussions Admin

list_processes

Retrieve a list of running processes with resource usage details. Filter by process name and sort by memory, CPU, or PID to quickly locate specific or high-usage processes.

Instructions

List running processes with resource usage.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of processes to return (1–200).
`sort_by`	No	Sort field — "memory", "cpu", "pid", or "name". Default: "memory".	memory
`filter_name`	No	Optional substring filter on process name.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read-only list operation and mentions resource usage, but does not explicitly state safety profile, default behavior, or that it returns a snapshot. This is adequate but minimal for a simple read operation.

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 a single sentence that conveys the essential purpose without any filler. Every word earns its place.

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?

Given the low complexity (3 optional params, no enums, output schema exists), the description is nearly complete. It is slightly terse but the schema covers parameters and the output schema covers returns. It missing explicit mention of filtering/sorting capabilities, but those are in the schema.

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%, so the baseline is 3. The description adds a hint about resource usage which relates to sort_by memory/cpu, but it does not explain any parameter semantics beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List running processes with resource usage' uses a specific verb ('list') and clear resource ('running processes'), and adds scope ('with resource usage') that distinguishes it from sibling tools like get_process (single process) and system-wide info tools (cpu_info, memory_info).

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that get_process should be used for individual process details, nor does it state any filtering or sorting capabilities that might affect selection.

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

Deploy Server