trace_list_processes
[external]
Lists local Windows processes, or diagnostics-published processes on other hosts. Inspect each target before capture.
From GliderTrace 1.0.0: expanded Windows inventory, target identities, and process capabilities.
Try it locally in the GliderTrace playground
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| includeSelf | boolean | No | Include the current GliderTrace server process. Defaults to false. Default: false |
| limit | number | No | Maximum number of process candidates to return. Default: 50 |
| skip | number | No | Offset from the previous nextSkip. Each page uses a fresh process list. Default: 0 |
| processId | number | No | Inspect one known PID, including an exited or unreadable target. |
Examples
Replace sample paths and symbol keys with values from your workspace.
List process candidates
{}Full MCP request
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "trace_list_processes",
"arguments": {}
}
}Response Notes
Returns process ids, names, start times, and warnings.
From GliderTrace 1.0.0: each item includes runtimeFamily, runtimeVersion, runtimeEvidence, architecture, accessState, diagnosticsPublished, and targetId. runtimeVersion identifies a loaded runtime module; it is not the application target framework. On macOS, runtimeEvidence can be diagnostics_publication and runtimeVersion remains unknown. An executable-only module list cannot prove a native process. Eligibility does not guarantee collector success. Unknown values remain unknown. A listed process is not necessarily eligible for capture.
capabilities lists each operation with backend, runtimeSupported, available, reason, guidance, helperAvailable, and policy. Null availability means the check is incomplete. GC dump helper availability remains unprobed in inventory. EventPipe, dump, and GC dump capture require CoreCLR. An ETW capability from GliderTrace 1.1.0 describes verified Framework IIS workers on Windows; local preflight still checks privilege, providers, and disk.
inventoryCoverage.scope is local_processes on Windows and diagnostics_published on other hosts. enumerationComplete describes enumeration; metadataComplete, inspectedCount, and metadataGapCount describe only the inspected page. Follow nextSkip with skip and retain your filters. Processes can start or exit between pages, so pages can overlap or omit changing entries. Refresh before selecting a target.
serviceNames contains observed accessible service associations. Missing associations do not prove that no service owns the process. iisAppPool identifies a pool only when the observed account identifies it reliably. A null pool does not exclude IIS, a custom account, or IIS Express. Check ownershipState and warnings. Workspace access does not authorize capture of every listed process.
GliderTrace 1.0.0 returns compact JSON for every tool. Result fields appear beside success; there is no response-format parameter. success describes the tool call. Check the process or session status and exitCode separately. Scalar results and fields that conflict with reserved names appear under result.
To migrate an envelope consumer, read response.sessionId instead of response.data.sessionId. Stored sessions and exported files keep their formats. --max-response-chars limits response text to 60,000 UTF-16 characters by default. Use 0 to disable it, or at least 1,000. This limit counts text characters, not transport bytes or tokens.
outputLimit.truncated marks omitted response detail. It does not change capture completeness. Use the returned next tool and arguments when available. Do not repeat a command or feedback submission to recover omitted output. For event pages, keep the filters and cursor while reducing limit.
For session details, set includeArtifacts and includeTopFindings to false to reduce output. Check error, actionable meta, warnings, and coverage before drawing conclusions. Internal diagnostics stay in local server logs.