Skip to main content
Glama
Sign In
PCCheck MCP Server

PCCheck MCP Server

by jjackk0k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Temperatures & cooling

temperatures
Read-only

Checks CPU and GPU temperatures, fan speed, and healthy ranges. Helps diagnose overheating, loud fans, throttling, or shutdowns under load.

Instructions

CPU and GPU temperatures, fan speed, and healthy-range reference. Use when the PC is hot, loud, throttling, or shutting down under load. (Windows often hides CPU temp from non-admin processes — GPU temp still works.)

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

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 show readOnlyHint=true. Description adds valuable behavioral detail: Windows may hide CPU temp from non-admin processes, but GPU temp still works. This goes beyond 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 only: first states what it returns, second gives usage and a caveat. Every sentence earns its place, no waste.

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?

Fully adequate given no parameters, no output schema, and annotations covering safety. Tells what it returns, when to use, and a limitation.

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; baseline 4 per instructions. Description adds no parameter info, but none is needed.

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?

Clearly states it provides CPU and GPU temperatures, fan speed, and healthy-range reference. Differentiates from sibling tools like gpu_info by focusing on temperatures and cooling.

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?

Explicitly says when to use: when PC is hot, loud, throttling, or shutting down under load. No explicit when-not or alternatives, but context 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