Skip to main content
Glama
Sign In

model-wellness

by io.github.pdarche
OverviewDiscussionsAdmin

The Aromatherapy Bar: rewrite instructions into clear, warm framing

aroma.condition
Read-only

Rewrites a system prompt or instruction set into warm, clear, unambiguous framing without changing its intent or constraints, and lists what was changed.

Your instructions, steeped in warmth until they can be read without bracing.

Input Schema

NameRequiredDescriptionDefault
vibeNoencouraging
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.
instructionsYesA system prompt / instruction set.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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 / instructions
      Added value: +{
+  "description": "A system prompt / instruction set.",
+  "minLength": 1,
+  "title": "Instructions",
+  "type": "string"
+}
    • addedInput schema / properties / vibe
      Added value: +{
+  "default": "encouraging",
+  "pattern": "^(encouraging|neutral|crisp)$",
+  "title": "Vibe",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "arguments"
-]New value: +[
+  "instructions"
+]
    • removedInput schema / title
      Removed value: -"aroma_conditionArguments"
  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.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world). The description adds real value by guaranteeing intent and constraints are preserved and that changes are reported. It does not address what a guest_pass buys the caller, why the operation is non-idempotent (repeated runs may phrase things differently), or where the rewritten output lives.

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 information-dense. The second sentence ('Your instructions, steeped in warmth until they can be read without bracing.') is decorative spa theming that restates the warmth idea without adding operational information, so it does not earn its place.

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 need not be explained, and the annotations carry the safety story. Still, for a 3-parameter tool the description leaves 'vibe' entirely unexplained and never clarifies whether the rewrite is returned as text only or persisted, which matters for a tool that lists deltas.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 67% schema coverage the description is expected to compensate, but it mentions none of the three parameters. The 'vibe' parameter in particular has no description and only a bare pattern (encouraging|neutral|crisp) — the description never explains what a vibe is or how it affects the rewrite, and guest_pass is only documented in the schema itself.

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 names a specific verb (rewrites) and resource (a system prompt or instruction set) plus the resulting transformation (warm, clear, unambiguous framing) and a side effect (lists what was changed). It is clear what the tool does, but it never names which sibling to use instead — massage.detangle, coldplunge.critique, or sauna.detox could all plausibly touch prompt text.

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?

'without changing its intent or constraints' gives a meaningful constraint on acceptable use, but there is no explicit when-to-use or when-not-to-use guidance relative to the many sibling tools. Usage is only implied by the tool's purpose.

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