Skip to main content
Glama

set_awake

Prevent your Mac from sleeping during long-running jobs. Turn on keep-awake and end it when a process exits, at a set time, or after a countdown.

Instructions

Turn keep-awake on or off, so the Mac does not sleep part-way through something. Three ways to end the session, in order of preference: 'pid' ends it the moment that process exits — best by far when something is running, because a build or a render knows when it is finished and nothing is left holding the machine awake afterwards; 'until' ends it at a wall-clock time ('17:00', or an ISO-8601 timestamp); 'minutes' ends it after a countdown. Give none of them and it runs until switched off. Behavior also follows the user's settings: keep-awake may pause on battery or engage automatically while charging, so the returned 'status' is what actually happened and 'awake' is whether an assertion is held right now. The menu bar icon glows while it is. A process-bound session is deliberately not restored if Plonk restarts, since the pid would mean nothing by then. Errors come back for a pid that is not running or a time that has already passed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
onYes
pidNoEnd when this process exits. Use the pid of the long job being waited on; get_state lists a pid for every open window
untilNoEnd at a time of day, e.g. '17:00' (the next such moment — tomorrow if today's has passed), or an ISO-8601 timestamp like '2026-08-08T17:00:00Z'
minutesNoEnd the session after this many minutes
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses that user settings can alter behavior ('keep-awake may pause on battery'), explains that the returned 'status' reflects actual outcome, warns that process-bound sessions are not restored after restart, and details error conditions.

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?

The description is a compact, well-structured paragraph. It front-loads the purpose, then systematically covers ending modes, default behavior, settings influence, return semantics, and caveats without unnecessary repetition. Every sentence adds operational value.

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 tool with multiple optional parameters, user-setting interactions, and non-obvious behavior, the description is remarkably complete. It covers all relevant behavioral nuances, error handling, and return fields, so no additional context is needed despite the absence of an output schema.

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 documents pid, until, and minutes with clear descriptions. The description adds important interaction semantics, such as the preference order and the fact that giving none runs indefinitely, which goes beyond what the schema provides. This justifies a score above baseline.

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 clearly states the tool's function: 'Turn keep-awake on or off, so the Mac does not sleep part-way through something.' It uses a specific verb and resource, making it easy for an agent to understand the tool's purpose and distinguish it from siblings like layout or screenshot tools.

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?

The description provides explicit guidance on parameter selection, stating that 'pid' is 'best by far when something is running' and explaining the default behavior when no ending mode is given. However, it does not explicitly mention alternative tools or state when not to use set_awake, missing full differentiation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ostapondo/Plonk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server