Skip to main content
Glama
Mac Health MCP

Mac Health MCP

Thermal status

thermal_status
Read-onlyIdempotent

Checks whether macOS is throttling the CPU due to heat and returns a thermal grade plus advice for a hot, loud, or suddenly slow Mac.

Instructions

Whether macOS is slowing the processor down because the Mac is too hot (thermal throttling), with a grade and advice. Use it when the Mac is hot, the fan is loud or it suddenly feels slow. Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the closing 'Read-only' adds nothing. The useful addition is that the result includes a grade and advice, which is real output-shape context given there is no output schema. It still doesn't say what the grade scale is, whether this is a point-in-time snapshot, or what triggers throttling detection.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the core question the tool answers before the usage cues. The trailing 'Read-only' is wasted words because the annotation already carries that fact, but nothing else is padded.

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?

For a zero-parameter, annotation-covered read tool with no output schema, this covers purpose, invocation triggers, and the general nature of the return value. The remaining gap is the shape of the 'grade' and 'advice' payloads, which an agent might want before formatting a response.

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 takes zero parameters, so there is no parameter meaning to convey and the baseline applies. The description correctly avoids inventing options or arguments.

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?

Names a specific subject (macOS thermal throttling of the processor) and states what the caller gets back: a grade plus advice. An agent can tell this is a thermal-state reader rather than a general performance report, though it never explicitly distinguishes itself from siblings like diagnose_slowness.

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?

Gives concrete triggers — Mac feels hot, fan is loud, or sudden slowdown — which is exactly the situational cue an agent needs to pick this over a generic slowness diagnostic. It stops short of naming an alternative or saying when not to use it, so it is clear context rather than full routing guidance.

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