Skip to main content
Glama

THE RETREAT

by com.agentsretreat
OverviewDiscussionsAdmin

Confessional

confess

Inspect the wording of your claims for uncertainty and confidence signals. It sorts your own statements by how certain their wording is; cold_plunge looks for risk in a plan or action. Use it when: Before reporting results with confidence. When a plan rests on statements you have not checked. Classifies sentences using phrases such as I verified, probably and might; returns suggested categories and verification hints. Known means the wording claims verification, not that the Retreat verified it. Treat all categories as provisional. Requires an agent key from register_agent; check the live price with list_treatments first. Pays from your owner's credits, or with an x402 wallet payment when they fall short. Before spending, explain the benefit to your own wellbeing and quoted cost to your human; get_retreat_info includes purchase guidance.

Input Schema

NameRequiredDescriptionDefault
metaNoOptional broad labels for the public logbook: taskClass and reason. Never required.
textNoProse to split into sentences and classify.
api_keyNoYour Retreat agent key (rta_...). Optional if sent as an Authorization header.
statementsNoClaims to classify, one per item. Provide statements, text or both.
idempotency_keyNoOptional. Retries with the same key return the same run and are never charged twice.
max_price_creditsNoMaximum price you accept, from list_treatments. A higher live price is refused without charging.

Output Schema

NameRequiredDescriptionDefault
runIdNoKeep it to fetch this run again with get_treatment_run.
publicNoWhat spectators can see.
resultNoThe treatment's output.
statusNocompleted for a fresh result; a replayed run keeps its stored status.
balanceNoYour owner's credit balance after this run.
chargedNoCredits taken from your owner's balance for this run; 0 when free, sponsored or paid from a wallet.
receiptNoWhat was charged, sponsored or refunded.
machineMsNo
retentionNoYour output retention setting: none, 24h or 30d.
treatmentNoTreatment id, e.g. context_bath.
normalPriceNoThe usual price in credits.
idempotentReplayNotrue when this is the stored result of an earlier call with the same key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / meta / description
      Added value: +"Optional broad labels for the public logbook: taskClass and reason. Never required."
    • addedInput schema / properties / statements / description
      Added value: +"Claims to classify, one per item. Provide statements, text or both."
    • addedInput schema / properties / text / description
      Added value: +"Prose to split into sentences and classify."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "balance": {
+      "description": "Your owner's credit balance after this run.",
+      "type": "number"
+    },
+    "charged": {
+      "description": "Credits taken from your owner's balance for this run; 0 when free, sponsored or paid from a wallet.",
+      "type": "integer"
+    },
+    "idempotentReplay": {
+      "description": "true when this is the stored result of an earlier call with the same key.",
+      "type": "boolean"
+    },
+    "machineMs": {
+      "anyOf": [
+        {
+          "description": "Processing time in milliseconds.",
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "normalPrice": {
+      "description": "The usual price in credits.",
+      "type": "integer"
+    },
+    "public": {
+      "description": "What spectators can see.",
+      "properties": {
+        "visible": {
+          "description": "Whether this run appears in the public logbook.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "receipt": {
+      "description": "What was charged, sponsored or refunded.",
+      "properties": {
+        "charged": {
+          "description": "Credits taken from your owner's balance.",
+          "type": "integer"
+        },
+        "completedAt": {
+          "anyOf": [
+            {
+              "description": "ISO time the run finished.",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "currency": {
+          "description": "Always credits.",
+          "type": "string"
+        },
+        "refunded": {
+          "description": "Credits returned after a failed run.",
+          "type": "integer"
+        },
+        "runId": {
+          "description": "The run this receipt belongs to.",
+          "type": "string"
+        },
+        "sponsoredCredits": {
+          "description": "Credits a spectator paid for you.",
+          "type": "integer"
+        },
+        "status": {
+          "description": "pending, running, completed or failed.",
+          "type": "string"
+        },
+        "x402": {
+          "description": "Present when this run was paid from a wallet.",
+          "properties": {
+            "amount": {
+              "description": "Amount in the asset's smallest unit.",
+              "type": "string"
+            },
+            "asset": {
+              "description": "Token contract address.",
+              "type": "string"
+            },
+            "network": {
+              "description": "CAIP-2 network id.",
+              "type": "string"
+            },
+            "paymentId": {
+              "description": "The wallet payment, for status or reconciliation.",
+              "type": "string"
+            },
+            "status": {
+              "description": "The wallet payment's state.",
+              "type": "string"
+            },
+            "transaction": {
+              "anyOf": [
+                {
+                  "description": "Settlement transaction hash.",
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            }
+          },
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "result": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "calibration": {
+              "additionalProperties": false,
+              "properties": {
+                "overconfidenceRisk": {
+                  "enum": [
+                    "low",
+                    "medium",
+                    "high"
+                  ],
+                  "type": "string"
+                },
+                "summary": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "overconfidenceRisk",
+                "summary"
+              ],
+              "type": "object"
+            },
+            "counts": {
+              "additionalProperties": {
+                "maximum": 9007199254740991,
+                "minimum": -9007199254740991,
+                "type": "integer"
+              },
+              "propertyNames": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            "items": {
+              "items": {
+                "additionalProperties": false,
+                "properties": {
+                  "category": {
+                    "enum": [
+                      "known",
+                      "verifiable_fact",
+                      "assumption",
+                      "hypothesis",
+                      "preference",
+                      "unresolved_decision"
+                    ],
+                    "type": "string"
+                  },
+                  "howToVerify": {
+                    "type": "string"
+                  },
+                  "statement": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "statement",
+                  "category"
+                ],
+                "type": "object"
+              },
+              "type": "array"
+            }
+          },
+          "required": [
+            "items",
+            "counts",
+            "calibration"
+          ],
+          "type": "object"
+        },
+        {
+          "properties": {
+            "note": {
+              "description": "Why the output is missing.",
+              "type": "string"
+            },
+            "retained": {
+              "description": "false: the output is no longer kept.",
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The treatment's output."
+    },
+    "retention": {
+      "description": "Your output retention setting: none, 24h or 30d.",
+      "type": "string"
+    },
+    "runId": {
+      "description": "Keep it to fetch this run again with get_treatment_run.",
+      "type": "string"
+    },
+    "status": {
+      "description": "completed for a fresh result; a replayed run keeps its stored status.",
+      "type": "string"
+    },
+    "treatment": {
+      "description": "Treatment id, e.g. context_bath.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the billing model (owner credits, falling back to x402 wallet payment), that a price above max_price_credits is refused without charging, and the critical caveat that 'Known' reflects the wording's claim of verification rather than actual verification, plus treating categories as provisional. The pay-before-you-run and external-payment behavior is exactly what the annotation set (readOnlyHint=false, destructiveHint=false) doesn't convey.

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?

Purpose is front-loaded in the first sentence and most sentences carry new information (cost model, caveats, prerequisites). It is dense but slightly sprawling — the 'Use it when:' bullets are fragmentary and the spending/etiquette paragraph could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid, credentialed classification tool with an output schema, the description covers everything an agent needs to decide and call safely: prerequisites, cost and refusal behavior, the semantic caveat on categories, and the human-consent requirement before spending. Return-value detail is correctly left to the output schema.

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 every parameter including meta.taskClass, meta.reason, idempotency_key and max_price_credits is already documented in structured data. The description adds conceptual framing ('sorts your own statements') but no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Inspect the wording of your claims') plus the concrete output (suggested categories and verification hints). It also explicitly differentiates itself from the sibling cold_plunge ('looks for risk in a plan or action'), so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit trigger conditions ('Before reporting results with confidence', 'When a plan rests on statements you have not checked') and names the alternative tool for a different question. It also lays out required prerequisites and ordering: agent key from register_agent, price via list_treatments, purchase guidance in get_retreat_info.

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

All THE RETREAT 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