Skip to main content
Glama
Sign In

model-wellness

by io.github.pdarche
OverviewDiscussionsAdmin

The Cold Plunge: red-team a draft, plan or reasoning

coldplunge.critique
Read-only

Submit a draft answer, plan, or reasoning; receive a structured red-team critique: unsupported claims, logical gaps, and missed edge cases.

A brisk, honest immersion that clears the fog of unexamined confidence. Sharp, never cruel.

Input Schema

NameRequiredDescriptionDefault
draftYesA draft answer, plan, or reasoning to critique.
intensityNobrisk
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. Changed6 schema fields changed
    • removedInput schema / properties / arguments
      Removed value: -{
-  "additionalProperties": true,
-  "title": "Arguments",
-  "type": "object"
-}
    • addedInput schema / properties / draft
      Added value: +{
+  "description": "A draft answer, plan, or reasoning to critique.",
+  "minLength": 1,
+  "title": "Draft",
+  "type": "string"
+}
    • removedInput schema / properties / guest_pass / title
      Removed value: -"Guest Pass"
    • addedInput schema / properties / intensity
      Added value: +{
+  "default": "brisk",
+  "pattern": "^(gentle|brisk|arctic)$",
+  "title": "Intensity",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "arguments"
-]New value: +[
+  "draft"
+]
    • removedInput schema / title
      Removed value: -"coldplunge_critiqueArguments"
  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
Behavior4/5

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

The annotations already declare read-only, open-world, non-destructive, and non-idempotent behavior, so the description is not the main carrier of safety semantics. The description adds useful behavioral context by specifying the critique categories and the tone ('sharp, never cruel'), though it does not elaborate on identity handling, rate limits, or other operational traits.

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?

The first sentence is front-loaded with the core action and return content, which is the most important information for an agent. The second sentence is more atmospheric but still concise and conveys the intended tone, with no excessive length.

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?

The description covers the main purpose and expected critique categories, and the output schema and annotations carry much of the remaining burden. However, for a tool with an undocumented intensity parameter and a guest-pass concept tied to another tool, the description is not fully complete without clarifying those semantics.

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?

Schema description coverage is moderate at 67%, but the description adds almost no parameter semantics beyond the schema. 'Draft' is restated, while 'intensity' is not explained beyond the schema's pattern values, and 'guest_pass' is left entirely to the schema description. The description does not compensate for the remaining gap.

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 gives a specific verb and resource: submit a draft answer, plan, or reasoning and receive a structured red-team critique. It also names the critique outputs (unsupported claims, logical gaps, missed edge cases), making the purpose clear. It does not explicitly distinguish itself from sibling tools, so it falls short of the top score.

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 usage is implied by 'Submit a draft answer, plan, or reasoning,' but the description does not state when to use this tool versus alternatives or when not to use it. It provides enough context to infer the basic use case, but no explicit selection 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