windows-debug-mcp

Overview Schema Source Related Servers Discussions Admin

get_startup_programs

Retrieves a list of startup programs, including Run keys, Startup folder, and logon tasks, to diagnose slow boot or background interference.

Instructions

Everything that starts with Windows: Run keys, the Startup folder and logon tasks.

The practical list to work through when boot is slow or something is interfering with games in the background.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 28, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It lists the types of items included (Run keys, Startup folder, logon tasks) which implies a read-only enumeration. However, it does not explicitly state whether the tool is destructive or requires permissions, though the read-only nature is inferred from context.

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?

Two sentences and a clear bullet-like phrase. Front-loaded with the essential information: what the tool lists. Every sentence is information-dense and necessary. No wasted words.

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?

The tool has no parameters and low complexity. The description covers typical use cases and content. An output schema exists (not shown) to document return values. Missing details like whether disabled items are included, but overall adequate for the tool's simplicity.

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

Parameters4/5

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

No parameters exist, so schema coverage is 100%. The description adds value by explaining the content of the output (list of startup programs with categories), compensating for the lack of parameters with clarity on what the tool returns.

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 clearly states the tool lists all startup items (Run keys, Startup folder, logon tasks). It distinguishes from siblings by specifying use cases like boot slowness and game interference, and the resource 'startup programs' is unique among sibling tools.

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 description explicitly guides when to use the tool: 'when boot is slow or something is interfering with games in the background.' It implies usage for troubleshooting but does not explicitly mention when not to use or provide alternatives, which is acceptable given the narrow scope.

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