spawnpoint

Set sleep after

set_sleep_after

Idempotent

Set how long a spawnpoint app stays awake after its last visit before it sleeps. An app on a machine (node, python, docker) sleeps when nobody visits for an hour by default, and the next visitor waits about half a minute while it starts. Pass minutes: a longer window keeps an app that is used in bursts awake between them; a shorter one lets a rarely used app sleep sooner; 0 goes back to the default. The plan sets the longest window, and a refusal says what it allows. To keep an app awake around the clock, use set_always_on instead. A static site never sleeps and has no window. get_project shows the window in use as sleep_after_minutes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "minutes": "<minutes>"
    },
    "name": "set_sleep_after"
  }
}

Input Schema

Name	Required	Description	Default
`minutes`	Yes	how many minutes with no visits before the app sleeps, at least 5; 0 goes back to the default
`project_id`	Yes	the id of the project

Output Schema

Name	Required	Description	Default
`note`	Yes
`project_id`	Yes
`sleep_after_minutes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 14, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations declare idempotent=true and destructive=false, but the description adds real context beyond them: the ~1 hour default, the ~30 second cold-start penalty, the plan-imposed ceiling, and that a refusal reports the allowed maximum. It stops short of saying whether a change affects an already-running instance immediately or only on the next visit, which is the one behavioral detail an agent might still want.

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?

The core action and its parameter come first, followed by context, tradeoffs, the alternative, and edge cases — a sensible order. It runs long for a two-parameter tool and the default-behavior sentence could be tightened, but no sentence is filler.

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?

With an output schema present, return values need not be explained, and the description still points to get_project for reading the current window via sleep_after_minutes. Defaults, plan limits, reset semantics, the always-on alternative, and the static-site exclusion leave nothing an agent needs to know before calling.

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?

Schema coverage is 100%, so the baseline is 3, but the description still adds meaning the schema lacks: the default is an hour, the window matters because of the cold-start wait, and 0 is a reset rather than a literal value. The minimum of 5 minutes lives only in the schema, but the description does not need to repeat it.

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?

States a specific verb+resource: it sets how long a spawnpoint app stays awake after its last visit before sleeping. It distinguishes itself from set_always_on and explicitly scopes out static sites, so an agent can separate it from siblings without opening the schema.

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?

Gives concrete selection guidance: a longer window suits bursty apps, a shorter one suits rarely used apps, and 0 restores the default. It names the alternative explicitly ('To keep an app awake around the clock, use set_always_on instead') and excludes static sites, which have no window.

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

All spawnpoint tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.