Skip to main content
Glama
jackalterman

Windows Diagnostics MCP Server

by jackalterman

analyze_startup_programs

Identify and analyze suspicious entries in Windows startup programs to enhance system security and stability using the Windows Diagnostics MCP Server.

Instructions

Analyze startup programs for suspicious entries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that runs a PowerShell script to scan startup programs from the Windows registry, processes the results, and returns formatted markdown content listing each program's name, command, location, user, verified status, and suspicious flags.
      export async function analyzeStartupPrograms() {
        const result = await runPowerShellScript(REGISTRY_SCRIPT, { ScanStartup: true, JsonOutput: true }) as AllTypes.RegistryDiagnosticResults;
        return {
          content: [
            {
              type: 'text',
              text: `# Startup Program Analysis
    
    ${result.StartupPrograms && result.StartupPrograms.length > 0 ? result.StartupPrograms.map(p => `- **Name**: ${p.Name}
      **Command**: ${p.Command}
      **Location**: ${p.Location}
      **User**: ${p.User}
      **Verified**: ${p.Verified}
      **Suspicious**: ${p.Suspicious}`).join('\n\n') : 'No startup programs found.'}`,
            },
          ],
        };
      }
  • Tool schema definition in the listTools response, specifying the tool name, description, and input schema (empty object, no required parameters).
      name: 'analyze_startup_programs',
      description: 'Analyze startup programs for suspicious entries',
      inputSchema: {
        type: 'object',
        properties: {},
      }
    },
  • src/index.ts:551-552 (registration)
    Registration in the CallToolRequest handler switch statement, dispatching calls to the analyzeStartupPrograms function from the registry module.
    case 'analyze_startup_programs':
      return await registry.analyzeStartupPrograms();
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'analyze' and 'suspicious entries,' implying a read-only diagnostic operation, but doesn't specify if it requires admin privileges, what 'suspicious' entails (e.g., malware, bloatware), or the output format (e.g., list, report). For a tool with zero annotation coverage, this lacks critical details about execution and results.

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, efficient sentence: 'Analyze startup programs for suspicious entries.' It's front-loaded with the core action and target, with zero wasted words. Every part of the sentence directly contributes to understanding the tool's function, making it highly concise and well-structured.

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?

Given the complexity of analyzing 'suspicious entries' (which could involve security, performance, or system health), the description is incomplete. No annotations exist to clarify behavior, and there's no output schema to explain return values. The description doesn't address what 'analyze' entails (e.g., scanning, reporting, flagging) or how results are presented, leaving significant gaps for effective tool use.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for zero parameters is 4, as the description appropriately focuses on the tool's purpose without redundant parameter explanations. No additional semantic value is required or provided.

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 tool's purpose: 'Analyze startup programs for suspicious entries.' It specifies the verb ('analyze'), resource ('startup programs'), and target ('suspicious entries'), which distinguishes it from siblings like 'scan_security_risks' or 'get_system_diagnostics.' However, it doesn't explicitly differentiate from 'scan_system_components' or 'find_orphaned_entries,' which could overlap in scope, preventing a perfect score.

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. With siblings like 'scan_security_risks' and 'scan_system_components,' it's unclear if this tool is for security-focused analysis, performance checks, or general diagnostics. There's no mention of prerequisites, context (e.g., post-infection scans), or exclusions, leaving usage ambiguous.

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

Related 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/jackalterman/windows-diagnostic-mcp-server'

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