Skip to main content
Glama
Sign In
PCCheck MCP Server

PCCheck MCP Server

by jjackk0k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Full PC checkup

full_checkup
Read-only

Run a complete PC health check to diagnose hardware specs, live performance, disk health, and more. Ideal for identifying causes of slowdowns or overall system health.

Instructions

Run a complete PC health checkup in one call: hardware specs, live CPU/RAM/GPU load, temperatures, disk space + disk health, crash history, antivirus status, startup programs, and network. Use for 'check my PC', 'why is my PC slow', 'is my computer healthy', or any broad diagnostic request. Takes ~20-30 seconds.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the time estimate (~20-30 seconds), which is helpful for planning. No contradictions with annotations.

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, no wasted words. Front-loaded with the main action and list of checks.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema, the description comprehensively lists what the tool covers. It is complete for an agent to decide when to invoke this tool versus sibling tools.

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 the baseline is 4. The description does not need to add parameter information.

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 uses a specific verb ('Run a complete PC health checkup') and lists numerous components (hardware specs, loads, temperatures, etc.), clearly distinguishing it from sibling tools by being comprehensive.

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?

It explicitly states when to use it ('Use for check my PC, why is my PC slow, is my computer healthy, or any broad diagnostic request') and gives a time estimate. It does not explicitly say when not to use it, but the context of sibling tools implies that for specific queries, one should use those instead.

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