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 confirmar=true; ask the person first. Whoever already bought it keeps their download.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSlug of YOUR template.
confirmNoRequired true. Retiring is PERMANENT: it cannot be undone or reactivated. Ask before using it.
confirmarNoDEPRECATED 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.

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.
previousSalesYesSales it got to have (counter).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses the irreversible nature, the effect on new sales, the requirement for user confirmation, and the outcome for prior purchasers. This is comprehensive behavioral disclosure for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the key action and consequences. Every sentence adds critical information; no filler or redundancy.

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 permanent, destructive tool with 100% schema coverage and an output schema, the description covers all necessary operational details: permanence, prerequisite confirmation, and impact on existing sales. The agent has everything needed to invoke it correctly.

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%, so the schema already documents all parameters, including deprecation and aliases. The description reinforces the requirement for confirmar=true but does not add new syntax details beyond that. Baseline 3 is appropriate given the high coverage.

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 clearly states the verb (RETIRES) and the resource (your template), and specifies the consequences (leaves catalog, no new sales, permanent). It distinguishes itself from sibling tools like set_template_active by emphasizing permanence and irreversibility.

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?

Explicitly instructs to ask the person first before using, and mandates confirmar=true (or confirm=true). This provides clear when-to-use guidance and a critical prerequisite, which is essential for a destructive action. It also clarifies that existing buyers are unaffected.

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