Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

retire_template

RETIRES one of your templates for good: it leaves the catalog, it takes no new sales and it can NOT be undone or reactivated. It requires confirm=true; ask the person first. Whoever already bought it keeps their download. If a lost dispute on that listing had already brought a wallet-born account to the threshold of lost disputes, retiring does not return its bond: the response then carries bondStatus = pending and a bondNote, and the committee decides.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSlug of YOUR template.
confirmYesRequired true. Retiring is PERMANENT: it cannot be undone or reactivated. Ask before using it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesAlways true: a refusal travels as an error.
noteYesWhat whoever already bought it keeps.
slugYesSlug of the retired template.
retiredYesAlways true: retiring is permanent.
bondNoteNoOnly present together with bondStatus: why the bond stays held.
bondStatusNoOnly present when THIS retirement held the listing bond: "pending" (same vocabulary as bondStatus in bond_data). It happens when a lost dispute on this listing had already brought the account to the threshold of lost disputes: retiring does not return the bond, the committee decides. Absent when there is no bond or it will be returned the ordinary way.
previousSalesYesSales it got to have (counter).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / bondNote
      Added value: +{
+  "description": "Only present together with bondStatus: why the bond stays held.",
+  "type": "string"
+}
    • addedOutput schema / properties / bondStatus
      Added value: +{
+  "description": "Only present when THIS retirement held the listing bond: \"pending\" (same vocabulary as bondStatus in bond_data). It happens when a lost dispute on this listing had already brought the account to the threshold of lost disputes: retiring does not return the bond, the committee decides. Absent when there is no bond or it will be returned the ordinary way.",
+  "enum": [
+    "pending"
+  ],
+  "type": "string"
+}
  2. Changed4 schema fields changed
    • removedInput schema / allOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "required": [
-          "confirm"
-        ]
-      },
-      {
-        "required": [
-          "confirmar"
-        ]
-      }
-    ]
-  }
-]
    • removedInput schema / properties / confirmar
      Removed value: -{
-  "deprecated": true,
-  "description": "DEPRECATED alias of `confirm`: it still works, but use `confirm` (it will be removed in a future round, no date yet). Required true. Retiring is PERMANENT: it cannot be undone or reactivated. Ask before using it.",
-  "type": "boolean"
-}
    • changedInput schema / required
      Previous value: -[
-  "slug"
-]New value: +[
+  "slug",
+  "confirm"
+]
    • removedInput schema / x-bernuvia-aliases
      Removed value: -{
-  "confirm": "confirmar"
-}
  3. Changed8 schema fields changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Obligatorio true. El retiro es PERMANENTE: no se puede deshacer ni reactivar. Pregunta antes de usarlo."New value: +"Required true. Retiring is PERMANENT: it cannot be undone or reactivated. Ask before using it."
    • changedInput schema / properties / confirmar / description
      Previous value: -"ALIAS RETIRADO de `confirm`: sigue funcionando, pero usa `confirm` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `confirm`. Obligatorio true. El retiro es PERMANENTE: no se puede deshacer ni reactivar. Pregunta antes de usarlo."New value: +"DEPRECATED alias of `confirm`: it still works, but use `confirm` (it will be removed in a future round, no date yet). Required true. Retiring is PERMANENT: it cannot be undone or reactivated. Ask before using it."
    • changedInput schema / properties / slug / description
      Previous value: -"Slug de TU plantilla."New value: +"Slug of YOUR template."
    • changedOutput schema / properties / note / description
      Previous value: -"Qué conserva quien ya la compró."New value: +"What whoever already bought it keeps."
    • changedOutput schema / properties / ok / description
      Previous value: -"Siempre true: una negativa viaja como error."New value: +"Always true: a refusal travels as an error."
    • changedOutput schema / properties / previousSales / description
      Previous value: -"Ventas que llegó a tener (contador)."New value: +"Sales it got to have (counter)."
    • changedOutput schema / properties / retired / description
      Previous value: -"Siempre true: el retiro es permanente."New value: +"Always true: retiring is permanent."
    • changedOutput schema / properties / slug / description
      Previous value: -"Slug de la plantilla retirada."New value: +"Slug of the retired template."
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: irreversible, no reactivation, existing buyers retain downloads, confirmation required, and the non-obvious bond consequence (bondStatus = pending plus bondNote, committee decides). That bond edge case is exactly the kind of behavioral detail an agent could not derive from the schema.

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?

Front-loads the decisive fact (permanent retirement) in the first clause, then layers preconditions and the bond exception. Dense but mostly earning its place; the final sentence about lost disputes is long and could be split, though the information is genuinely non-obvious.

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 an irreversible mutation with no annotations, the description covers what is destroyed, what survives (existing buyers' downloads), the required confirmation, and the one exceptional return state. With an output schema present it correctly does not waste space explaining ordinary return values.

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% and both parameters are already documented, including the confirm=true requirement and its permanence warning. The description reinforces the confirmation semantics and adds the 'ask the person first' social guidance, but adds no new syntax or format meaning. Baseline 3 applies when the schema does the heavy lifting.

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 ('RETIRES one of your templates') and immediately pins down the scope: leaves the catalog, takes no new sales, cannot be undone or reactivated. That permanence framing cleanly separates it from the reversible siblings set_template_active and update_published_template without naming them.

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

Usage Guidelines4/5

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

Gives a clear precondition ('requires confirm=true; ask the person first') and an implied when-not: this is the permanent route rather than the deactivate/reactivate route. It never explicitly names an alternative tool, so the agent must infer that set_template_active is the non-destructive option.

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

All Bernuvia toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources