MCP Mac Monitor

Poner la Mac en reposo

sleep

Destructive

Save battery by setting your Mac to low-power mode instantly or after a delay, without closing applications. Cancellable grace period prevents accidental triggers.

Instructions

Pone la Mac en reposo (sleep), ahora o dentro de X minutos (mínimo 60 s). Casi no gasta batería y no cierra las apps. Ojo: al dormir, Claude en esta Mac deja de responder hasta que alguien la despierte. Cancelable con cancel_power_action.

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

Input Schema

Name	Required	Description	Default
`delay_minutes`	No	Minutos de espera antes de ejecutar. 0 = en 60 segundos (margen para que llegue la respuesta).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description reveals key behavioral effects: negligible battery drain, apps remain open, Claude becomes unresponsive until the Mac is woken, and the action is cancelable. This is exactly the kind of context an agent needs to anticipate consequences.

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?

Three sentences, no filler: the first states the action and timing, the second covers side effects, the third delivers the critical warning and the cancel path. Every sentence earns its place and the most important caveat is highlighted with 'Ojo'.

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 simple one-parameter power action with no output schema, the description is complete. It covers what happens, when it happens, side effects, the impact on Claude's availability, and cancellation. The annotations already cover the destructive/read-only profile, so nothing crucial 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 schema already fully describes delay_minutes, including the 0-means-60s behavior, so the baseline is 3. The description adds the clarifying 'mínimo 60 s' and explains the 'now or in X minutes' semantics, reinforcing the schema's meaning and resolving the potential ambiguity of delay_minutes=0.

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?

The description states the exact action: 'Pone la Mac en reposo (sleep)', with clear resource and verb. It also differentiates from siblings by noting it 'no cierra las apps' and 'Casi no gasta batería', contrasting with shutdown/restart, and references cancel_power_action for cancellation.

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?

Provides clear context: immediate or delayed execution, a minimum delay, and the ability to cancel via cancel_power_action. It also includes a when-not-to-use caveat (Claude stops responding while asleep), though it does not explicitly contrast with shutdown/restart or lock_screen.

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

Deploy Server