Skip to main content
Glama

Keep the Mac awake

keep_awake

Keeps your Mac awake on demand, either until Claude Desktop quits or for a set number of hours, and lets you turn it off or check the current status.

Instructions

Keep the Mac awake (caffeinate -dims): mode on (until Claude desktop quits, or for hours), off, or status.

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

Input Schema

NameRequiredDescriptionDefault
modeNoon (default) starts keeping it awake, off stops, status reports
hoursNowith on: stop after this many hours (default 0: until Claude desktop quits)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.3
    • addedInput schema / properties / hours / description
      Added value: +"with on: stop after this many hours (default 0: until Claude desktop quits)"
    • addedInput schema / properties / mode / description
      Added value: +"on (default) starts keeping it awake, off stops, status reports"
  2. First observedv0.7.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false but destructiveHint=false, and the description usefully adds the persistence lifetime ("until Claude desktop quits") plus the exact caffeinate flags (-dims), which is genuine context beyond the annotations. It stops short of disclosing the practical consequence of a state-mutating tool — battery/power impact, whether the state survives across sessions, or whether the agent should clean up after itself.

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?

A single dense sentence with a front-loaded verb+resource and the flags in a parenthetical. Every clause carries information, though the nested parentheses around mode and hours make it slightly harder to parse than a short clause list would be.

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 two-parameter, zero-required toggle tool with full schema coverage and no output schema, the definition covers what is needed to invoke it correctly. The only gap is that the status mode's report contents are not described, which would help an agent interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are fully documented with enums and bounds in the schema itself; the description largely restates them. Its one small addition is linking the two parameters (a duration applies only to mode=on, otherwise it runs until the desktop app quits), which the schema also states, so baseline 3 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 a specific verb and resource — keeping the Mac awake — and even names the underlying mechanism (caffeinate -dims), so an agent knows exactly what the tool does. It doesn't explicitly contrast itself with siblings, but no sibling in the list plausibly overlaps, so disambiguation risk is low.

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?

The three modes (on/off/status) are enumerated, which implies the call patterns, but there is no statement of when to prefer this tool or when not to use it — e.g., no note that 'on' should be paired with a later 'off' or that hours=0 persists until the desktop app quits. Usage is implied rather than guided.

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