Skip to main content
Glama
Sign In
PCCheck MCP Server

PCCheck MCP Server

by jjackk0k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Crash history & stability

crash_report
Read-only

Diagnose Windows stability issues by analyzing recent crash data, antivirus status, pending reboot, and disk health.

Instructions

Windows stability report: blue screens and unexpected shutdowns (last 30 days), app crashes (last 14 days), antivirus status, pending-reboot state, and disk SMART health. Use for crashes, freezes, random restarts, blue screens, or 'my PC turned itself off'.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context by specifying time ranges (30 days for crashes, 14 days for app crashes) and included data like SMART health, which is not in annotations. No contradictions.

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: one lists all data points, the second gives clear use cases. No filler words. Efficient and front-loaded.

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 description covers purpose, usage, and data scope. No output schema exists, but the tool is simple. Could optionally mention output format, but not required for completeness.

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, and schema coverage is 100%. The description adds no parameter info, which is appropriate. Baseline of 4 for no parameters.

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 is highly specific, listing exactly what the tool covers (blue screens, app crashes, antivirus, etc.) and clearly distinguishes it from sibling tools like battery_health or performance_snapshot. The tool name and title align well.

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 states when to use the tool: 'for crashes, freezes, random restarts, blue screens, or 'my PC turned itself off''. It does not mention when not to use it or alternatives, but given the focused scope and sibling tools, the guidance is clear.

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

Deploy Server

Other Tools