Skip to main content
Glama
Sign In
Mac Health MCP

Mac Health MCP

by Swedishwizards
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Disk report

disk_report
Read-onlyIdempotent

Checks startup disk free space, grades it, warns when low, and lists home folders by size while only reading data and never deleting files.

Instructions

Free space on the startup disk with a grade and warning when it gets low, plus the largest folders in the home folder (shown as ~/Library, ~/Downloads …). Only reads sizes, never deletes anything. Measuring the home folder can take up to about 20 seconds; if it takes longer the tool answers with what it has. Folders protected by macOS are skipped and reported.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and idempotentHint, so safety is covered; the description still adds real value beyond them by disclosing the ~20 second measurement window, that a partial answer is returned on timeout, and that macOS-protected folders are skipped and reported. The one thing not covered is the shape of the result, which the description only sketches.

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?

Four tight sentences, front-loaded with what is reported, then the non-destructive guarantee, then latency and degradation behavior, then edge cases. Every sentence carries information an agent would otherwise have to discover by trial.

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?

With no output schema, the description still tells the agent what comes back (grade, warning, largest folders) and how the result can be partial or missing protected folders. For a zero-parameter read-only report tool, nothing material is left unexplained.

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 nothing for the description to disambiguate; the baseline of 4 applies. The parenthetical about how folders appear (~/Library, ~/Downloads) is a minor extra but concerns output, not 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?

States a concrete resource (free space on the startup disk, largest folders in the home folder) with the exact outputs produced (a grade plus a low-space warning). An agent can immediately distinguish this from battery_report, memory_report, or top_processes without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the description makes clear this is the disk-space check, but it names no alternatives and gives no explicit when-to-use/when-not guidance against siblings like get_mac_overview. Adequate but leaves routing to inference.

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