Skip to main content
Glama

set_awake

Prevent unwanted sleep during builds or renders by tying the keep-awake session to a process exit, an exact time, or 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 may pause or auto-enable keep-awake, that the returned 'status' reflects reality, that the menu bar icon glows, that process-bound sessions are not restored after restart, and that errors occur for invalid pids or past times.

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 substantial but every sentence earns its place: purpose, end-condition modes, external settings, return semantics, restart behavior, and error cases. It is front-loaded with the core purpose and then logically organized.

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?

Given the tool has moderate complexity, no annotations, and no output schema, the description covers all essential context: what the tool does, how each parameter behaves, what the response fields mean, and what error cases exist. It is sufficient for an agent to select and invoke the tool correctly.

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

Parameters5/5

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

The description adds meaningful semantics beyond the schema, such as the preference ordering among pid/until/minutes, the 'best by far' guidance for running jobs, and the caveat about process-bound sessions not surviving restart. The schema descriptions are good, but the tool description enriches their practical meaning.

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 opens with a specific verb+resource: 'Turn keep-awake on or off, so the Mac does not sleep part-way through something.' This clearly distinguishes set_awake from sibling tools like get_state, set_active, or workspace/layout tools.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance by ranking the three end conditions in order of preference and explaining that 'pid' is 'best by far when something is running.' It also states the behavior when none are given, which covers the full usage space.

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