Skip to main content
Glama
Sign In
Mac Health MCP

Mac Health MCP

by Swedishwizards
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Memory report

memory_report
Read-onlyIdempotent

Diagnose whether low RAM or memory pressure is making a Mac sluggish by reviewing swap, compressed memory, and file cache in a read-only plain-Swedish report with a grade.

Instructions

Memory pressure, swap, compressed memory and file cache, explained in plain Swedish with a grade ("Bra", "Okej", "Behöver åtgärd"). Use it when the user wonders if their Mac has enough RAM or why it is sluggish. 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": "memory_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered and the trailing 'Read-only' is largely redundant. What the description does add is genuine behavioral context: the output is prose in Swedish and includes a graded verdict ('Bra', 'Okej', 'Behöver åtgärd'), which tells the agent what kind of result to expect and how to relay it.

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: content coverage first, then the trigger, then the safety tag. The only waste is the final 'Read-only', which merely restates an annotation the agent already receives.

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?

For a zero-parameter, read-only diagnostic with no output schema, the description supplies everything needed: which memory facets are reported, that the result is Swedish prose plus a grade, and when to reach for it. No unresolved gaps remain for an agent to call it correctly.

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 no parameters and the schema is an empty object with additionalProperties false, so there is no parameter semantics to explain. Baseline 4 applies.

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?

The description names the resource (memory) and enumerates exactly what the report covers — pressure, swap, compressed memory, file cache — plus the grade output, which separates it from batched siblings like battery_report and disk_report. It stops short of explicitly distinguishing itself from diagnose_slowness, which the stated 'why it is sluggish' use case clearly overlaps.

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?

It does state a usage context ('when the user wonders if their Mac has enough RAM or why it is sluggish'), which is better than nothing. But that second trigger plausibly belongs to diagnose_slowness, and the description offers no exclusion or routing rule, leaving the agent to guess between two adjacent tools.

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