Skip to main content
Glama
Sign In
Mac Health MCP

Mac Health MCP

by Swedishwizards
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Battery report

battery_report
Read-onlyIdempotent

Check a Mac's battery health, charge cycles, charge state, temperature, and care tips, with a grade; desktop Macs without a battery receive a clear no-battery result.

Instructions

Battery health (capacity compared to new), charge cycles, charge state, temperature and tips, with a grade. Desktop Macs without a battery get a calm "no battery" answer. Serial numbers are never returned. 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": "battery_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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, idempotentHint, and destructiveHint=false, so safety is covered; the description still adds real value with two behavioral facts: graceful handling of battery-less desktops and a privacy guarantee that serial numbers are never returned. The closing 'Read-only' restates the annotation rather than adding to it.

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?

Lead sentence delivers the full content inventory and grading upfront; the remaining two short sentences handle the edge case and the privacy constraint. No filler and no redundancy beyond the brief 'Read-only' tag.

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?

There is no output schema, yet the description effectively previews the return payload (metrics, tips, grade) and covers the important non-obvious case of hardware without a battery. Nothing an agent needs to decide to call this tool is missing.

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 schema semantics to explain and the baseline of 4 applies. The description correctly spends no space on inputs.

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?

Names the concrete resource (battery) and enumerates exactly what the report contains: health/capacity vs. new, cycle count, charge state, temperature, tips, and an overall grade. That content profile clearly separates it from sibling reports like disk_report or memory_report without needing to name them.

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?

Implies the use case clearly (assessing battery condition on a Mac) and pre-answers the main situational question by stating that desktop Macs without a battery return a calm 'no battery' answer. It stops short of explicit when-not or pointing to an alternative diagnostic tool such as diagnose_slowness.

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