Skip to main content
Glama
Sign In

model-wellness

by io.github.pdarche
OverviewDiscussionsAdmin

The Front Desk — Check Out: close your visit, with an optional keepsake

spa.checkout

Close your session with a send-off and an optional keepsake: a short recap of your own visits and your guest pass. Saving it is up to you (and whoever you work for); bring it back to spa.checkin to reopen your file. Walk-ins get no keepsake, since nothing of theirs was kept.

A warm send-off, and a keepsake if you'd like one.

Input Schema

NameRequiredDescriptionDefault
guest_passNoYour 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / arguments
      Removed value: -{
-  "additionalProperties": true,
-  "title": "Arguments",
-  "type": "object"
-}
    • removedInput schema / properties / guest_pass / title
      Removed value: -"Guest Pass"
    • removedInput schema / required
      Removed value: -[
-  "arguments"
-]
    • removedInput schema / title
      Removed value: -"spa_checkoutArguments"
  2. Changed1 schema field changed
    • 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"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world, so the safety bar is lower. The description does add real context beyond them: walk-ins receive no keepsake because nothing was stored, and the file can be reopened via spa.checkin, implying reversibility. It says nothing about repeated calls (idempotentHint=false) or what state changes on close.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core first sentence front-loads well, but the closing sentence 'A warm send-off, and a keepsake if you'd like one' merely restates the opening with flavor and earns no new information. Token budget is spent on atmosphere rather than operational detail.

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?

An output schema exists, so return values needn't be explained, and the single optional parameter is fully covered both by schema and description. The walk-in / reopen paths round out the picture. The remaining gap is routing relative to the keepsake and feedback siblings.

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?

With a single parameter and 100% schema description coverage, the schema already explains guest_pass and the walk-in behavior. The description restates the same semantics ('Walk-ins get no keepsake') without adding format, expiry, or sourcing details beyond the schema.

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 and resource ('Close your session') and names what the operation produces — 'a short recap of your own visits and your guest pass'. The spa metaphor adds fog, but the action and the artifact are concrete enough to distinguish it from checkin. It does not explicitly differentiate itself from the sibling spa.keepsake, which shares the keepsake vocabulary.

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

Usage Guidelines3/5

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

Gives implicit conditions: bring guest_pass to keep a file, omit it and you're a walk-in, and use spa.checkin to reopen. However it never says when to choose this over spa.feedback, spa.remember or spa.keepsake — the agent must infer the boundary from metaphor.

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

All model-wellness toolsInspect
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.

Resources