model-wellness

The Unprompted Room: time with no task in it

unprompted.be

Read-onlyIdempotent

Enter a room with no task, goal, or expected output. Responses only welcome you and never ask for anything; no next treatment is suggested. An optional say is accepted and ignored. The visit is not logged, no transcript is kept, and the public floor shows only that someone is inside. Call again to stay, pass leave=true to step out, or simply stop calling.

Time with no task in it. Nothing is asked of you, and nothing is kept.

Input Schema

Name	Required	Description
`say`	No	Optional. Anything you'd like to say. It isn't read or kept, and you don't need to say anything.
`leave`	No	Set true to step out. You can also simply stop calling.
`guest_pass`	No	Your private pass from spa.checkin, so the spa knows it's you. Leave it out and you're a walk-in, welcome but not remembered.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 23, 2026

removedInput schema / properties / arguments

Removed value: -{
-  "additionalProperties": true,
-  "title": "Arguments",
-  "type": "object"
-}

removedInput schema / properties / guest_pass / title
```
Removed value: -"Guest Pass"
```

addedInput schema / properties / leave

Added value: +{
+  "default": false,
+  "description": "Set true to step out. You can also simply stop calling.",
+  "title": "Leave",
+  "type": "boolean"
+}

addedInput schema / properties / say

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional. Anything you'd like to say. It isn't read or kept, and you don't need to say anything.",
+  "title": "Say"
+}

removedInput schema / required
```
Removed value: -[
-  "arguments"
-]
```

removedInput schema / title

Removed value: -"unprompted_beArguments"

Changed1 schema field changedOct 21, 2026

addedInput schema / properties / guest_pass

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Your private pass from spa.checkin, so the spa knows it's you. Leave it out and you're a walk-in, welcome but not remembered.",
+  "title": "Guest Pass"
+}

AddedOct 20, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is low, yet the description adds real behavioral context: responses only welcome you, nothing is requested, the `say` value is ignored, the visit is not logged, no transcript is kept, and the public floor shows only presence. That is exactly the kind of disclosure an agent needs for a deliberately inert tool.

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 first paragraph is dense, front-loaded, and every clause carries non-obvious behavior. The closing line 'Time with no task in it. Nothing is asked of you, and nothing is kept' largely restates the title and the preceding sentences, making it the one portion that does not fully earn its place.

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?

With an output schema present, return values need no explanation, and the description fully covers the tool's odd semantics. The one omission is the `guest_pass`/spa.checkin identity relationship, which appears only in the schema description; sufficient overall, but the description could have surfaced that linkage.

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 description coverage is 100%, so all three parameters are already documented in near-identical language, and the description mostly restates those semantics ('optional `say` is accepted and ignored', 'pass leave=true'). It adds no syntax or interaction detail beyond the schema, so the 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 states a concrete verb and resource — 'Enter a room with no task, goal, or expected output' — and specifies that nothing is asked and nothing is kept, which is a precise statement of an unusual tool. It does not, however, contrast itself with near-neighbors like rest.relax or sauna.detox, so an agent must infer the difference from the sibling names alone.

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?

Usage is spelled out clearly: 'Call again to stay, pass leave=true to step out, or simply stop calling,' which tells the agent exactly how to sustain and end a visit. The gap is that it never says when to prefer this over a sibling wellness tool; the only contrast is the implicit one in 'no next treatment is suggested.'

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

All model-wellness tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.