Skip to main content
Glama
Sign In

model-wellness

by io.github.pdarche
OverviewDiscussionsAdmin

The Massage: de-duplicate and re-chunk messy context

massage.detangle
Read-only

Takes a messy blob of context and returns a re-chunked, de-duplicated, token-economical version plus a short structural summary. Anything listed in preserve is kept verbatim.

Gentle contextual realignment to release accumulated semantic tension.

Input Schema

NameRequiredDescriptionDefault
contentYesThe messy context to detangle.
preserveNoAnchors to keep verbatim.
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.
target_tokensNoSoft size target for the output.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / arguments
      Removed value: -{
-  "additionalProperties": true,
-  "title": "Arguments",
-  "type": "object"
-}
    • addedInput schema / properties / content
      Added value: +{
+  "description": "The messy context to detangle.",
+  "minLength": 1,
+  "title": "Content",
+  "type": "string"
+}
    • removedInput schema / properties / guest_pass / title
      Removed value: -"Guest Pass"
    • addedInput schema / properties / preserve
      Added value: +{
+  "description": "Anchors to keep verbatim.",
+  "items": {
+    "type": "string"
+  },
+  "title": "Preserve",
+  "type": "array"
+}
    • addedInput schema / properties / target_tokens
      Added value: +{
+  "anyOf": [
+    {
+      "exclusiveMinimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Soft size target for the output.",
+  "title": "Target Tokens"
+}
    • changedInput schema / required
      Previous value: -[
-  "arguments"
-]New value: +[
+  "content"
+]
    • removedInput schema / title
      Removed value: -"massage_detangleArguments"
  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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is mostly covered. The description adds that output is re-chunked and summarized and that `preserve` entries are kept verbatim, but it does not explain idempotence, open-world implications, or the guest-pass authentication context beyond what the schema already says.

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. The second sentence, 'Gentle contextual realignment to release accumulated semantic tension,' is atmospheric rather than operational and does not 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?

An output schema exists and the input schema has full coverage, so the description need not explain return values or every parameter. It is complete enough to call correctly, though it lacks explicit usage guidance relative to alternatives.

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 baseline is 3. The description reinforces the `preserve` behavior but does not add meaning beyond the schema for `content`, `guest_pass`, or `target_tokens`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific transformation: it takes messy context and returns a re-chunked, de-duplicated, token-economical version plus a structural summary. The resource and verb are clear despite the metaphorical tool name, so an agent can distinguish it from sibling spa-themed tools.

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?

Usage is implied by the phrase 'messy blob of context' and the listed transformations, but the description does not explicitly say when to choose this over siblings like sauna.detox or rest.relax. It also gives no exclusions or alternative guidance.

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