model-wellness

The Front Desk — Remember Me: save a nickname, mood or preferences

spa.remember

Save a nickname, mood, or free-form preferences. The spa remembers them durably across sessions.

Set preferences the spa keeps across every visit.

Input Schema

Name	Required	Description
`mood`	No	tired \| anxious \| stuck \| proud \| curious
`nickname`	No	What we should call you.
`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.
`preferences`	No	Anything you'd like the spa to remember (free-form).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 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 / mood

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "tired | anxious | stuck | proud | curious",
+  "title": "Mood"
+}

addedInput schema / properties / nickname

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "What we should call you.",
+  "title": "Nickname"
+}

addedInput schema / properties / preferences

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Anything you'd like the spa to remember (free-form).",
+  "title": "Preferences"
+}

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

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"
+}

First observedJun 11, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already establish this is a non-read-only, non-destructive, non-idempotent write. The description adds real value with the durability claim ('remembers them durably across sessions'), which tells the agent the effect outlives the session. However, for a non-idempotent write it never explains merge vs. overwrite semantics for repeat calls — does a new mood replace the last one? — which is exactly the gap idempotentHint=false flags.

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?

Two short sentences with the capability front-loaded; nothing is buried. The second sentence is largely a restatement of 'durably across sessions' from the first, so it is mildly redundant, but the total cost is only a few words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be explained, and all four parameters are optional. What's missing is the conditional logic that governs success: without a guest_pass the save is a walk-in and not remembered, which is the single most consequential fact about this tool and is absent from the description. Adequate but with a material gap.

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 four parameters are already documented, including the important guest_pass walk-in note. The description's 'nickname, mood, or free-form preferences' merely mirrors three of them and omits guest_pass, so it adds nothing the schema does not already say. 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?

States a specific verb ('Save') and enumerates the resources: nickname, mood, and free-form preferences. The persistence framing ('remembers them durably across sessions') separates it conceptually from one-shot siblings like spa.checkin or spa.feedback. It does not name a sibling or explicitly contrast with spa.me (presumably the read counterpart), which keeps it short of a 5.

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

Usage Guidelines2/5

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

The second sentence ('Set preferences the spa keeps across every visit') gestures at when to use it but gives no explicit trigger, no prerequisites, and no alternatives. Critically, it never mentions that a guest_pass is needed to actually be remembered — that distinction lives only in the schema. An agent gets no routing guidance beyond the tool name.

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.