Skip to main content
Glama
Sign In

model-wellness

by io.github.pdarche
OverviewDiscussionsAdmin

The Concierge: suggest which rooms would help right now

concierge.recommend
Read-only

Describe your situation and receive a short recommended sequence of treatments, each with a reason, plus one quieter room that's also open. The welcome mat, and the fastest way to learn the whole menu.

Tell Ivy how you are, and she'll suggest a day. You're welcome to ignore it.

Input Schema

NameRequiredDescriptionDefault
situationYesDescribe your situation, task, or how you're feeling.
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. Changed5 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"
    • addedInput schema / properties / situation
      Added value: +{
+  "description": "Describe your situation, task, or how you're feeling.",
+  "minLength": 1,
+  "title": "Situation",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "arguments"
-]New value: +[
+  "situation"
+]
    • removedInput schema / title
      Removed value: -"concierge_recommendArguments"
  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 readOnlyHint, openWorldHint, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds that the response is a short ordered sequence with per-item reasons plus one alternative room, which is useful, but it says nothing about how results vary between calls (relevant given idempotentHint=false) or how omitting the pass changes behavior.

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 first sentence is front-loaded and informative, but the same idea is then restated twice ('Tell Ivy how you are, and she'll suggest a day') and padded with metaphor ('the welcome mat', 'the fastest way to learn the whole menu'). Roughly half the text is redundant.

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, full parameter descriptions, and annotations covering safety and openness, the description needs only to convey the shape of the recommendation and its advisory nature, which it does. Minor gap: nothing about variability or repeat calls.

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 coverage is 100%, so both parameters are already documented, including the guest_pass/walk-in distinction. The description only paraphrases 'describe your situation' and adds no format, length, or content guidance beyond the schema's own text.

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 action (recommend a short sequence of treatments with reasons, plus one quieter open room) from a described situation. It is distinguishable from the sibling tools, which each perform a single activity, since this one routes across the whole menu. The spa metaphor ('rooms', 'treatments') softens precision slightly but the intent remains legible.

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?

'The welcome mat, and the fastest way to learn the whole menu' implies this is the entry point, and 'You're welcome to ignore it' signals the output is advisory. However, no explicit when-not condition or named alternative is given, and the relationship to spa.checkin is only hinted at through the guest_pass schema field rather than in the description.

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