Skip to main content
Glama
jackalterman

Windows Diagnostics MCP Server

by jackalterman

get_bsod_events

Retrieve and analyze Blue Screen of Death (BSOD) events from Windows systems within a specified time frame to diagnose crashes and improve stability.

Instructions

Get Blue Screen of Death (BSOD) events

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysBackNoNumber of days back to analyze (default: 7)

Implementation Reference

  • Core implementation of the get_bsod_events tool. Executes a PowerShell diagnostic script to retrieve BSOD events from Windows Event Logs and formats them into a markdown response.
    export async function getBSODEvents(args: { daysBack?: number }) {
      const daysBack = args?.daysBack || 7;
      const result = await runPowerShellScript(DIAGNOSTIC_SCRIPT, { DaysBack: daysBack, JsonOutput: true }) as AllTypes.DiagnosticResults;
    
      return {
        content: [
          {
            type: 'text',
            text: `# Blue Screen of Death (BSOD) Events (Last ${daysBack} days)\n\n${result.BSODEvents.length > 0 ? 
    `⚠️ **CRITICAL**: ${result.BSODEvents.length} BSOD event(s) found!\n\n` + result.BSODEvents.map((e: AllTypes.EventInfo) => `- **${e.Time}**: ${e.Description} (Event ID: ${e.EventID}, Source: ${e.Source})\n  Details: ${e.Details.substring(0, 200)}...`).join('\n\n')
    : '✅ No BSOD events found in the specified period.'}`,
          },
        ],
      };
    }
  • src/index.ts:82-95 (registration)
    Tool registration in the MCP listTools handler, defining the tool name, description, and input schema.
    {
      name: 'get_bsod_events',
      description: 'Get Blue Screen of Death (BSOD) events',
      inputSchema: {
        type: 'object',
        properties: {
          daysBack: {
            type: 'number',
            description: 'Number of days back to analyze (default: 7)',
            default: 7,
          },
        },
      },
    },
  • src/index.ts:543-544 (registration)
    Dispatcher in the MCP callTool handler that routes get_bsod_events calls to the diagnostics module implementation.
    case 'get_bsod_events':
      return await diagnostics.getBSODEvents(args as { daysBack?: number });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states what the tool does ('Get BSOD events') without mentioning permissions needed, rate limits, response format, or whether it's a read-only operation. This is inadequate for a tool that likely accesses system data, as it omits critical behavioral traits.

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 with zero waste, front-loading the core purpose ('Get Blue Screen of Death (BSOD) events'). It's appropriately sized for a simple tool, making it easy to parse without unnecessary elaboration.

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 retrieving system events, the lack of annotations and output schema means the description should compensate by explaining behavioral aspects like permissions or response format. It fails to do so, leaving gaps in understanding how the tool operates and what it returns, making it incomplete for effective agent use.

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?

The input schema has 100% description coverage, clearly documenting the 'daysBack' parameter with its default and type. The description adds no additional parameter semantics beyond what the schema provides, such as format details or constraints. Given the high schema coverage, a baseline score of 3 is appropriate as the schema handles the heavy lifting.

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 verb 'Get' and the resource 'Blue Screen of Death (BSOD) events', making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'get_shutdown_events' or 'get_system_diagnostics', which might also retrieve system events, leaving room for ambiguity in tool selection.

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, such as sibling tools like 'get_shutdown_events' or 'analyze_system_stability'. It lacks context on prerequisites, exclusions, or specific scenarios where retrieving BSOD events is appropriate, leaving the agent without usage direction.

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