Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

delete_draft

DELETES the saved publish draft (there is ONE per account). It requires confirm=true and cannot be undone: show what is there first with my_draft and ask the person, above all if it is an EDIT draft (that would be pending changes to an already published template). It is what lets you start another one with create_draft without going through the website.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmYesRequired true. The draft is lost and cannot be recovered: look first at what it holds with my_draft and ask the person.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesAlways true: no draft is left saved.
noteNoExactly what has been lost, in one sentence.
deletedYesIt really was deleted in this call.
hadDraftYesThere was a draft before this call.
wasEditingNoSlug the deleted draft was editing, or null if it was for a new template.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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. The draft is lost and cannot be recovered: look first at what it holds with my_draft and ask the person.",
-  "type": "boolean"
-}
    • addedInput schema / required
      Added value: +[
+  "confirm"
+]
    • removedInput schema / x-bernuvia-aliases
      Removed value: -{
-  "confirm": "confirmar"
-}
  2. Changed7 schema fields changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Obligatorio true. El borrador se pierde y no se puede recuperar: mira antes qué tiene con my_draft y pregunta a la persona. / Required true; the draft is lost for good."New value: +"Required true. The draft is lost and cannot be recovered: look first at what it holds with my_draft and ask the person."
    • 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 borrador se pierde y no se puede recuperar: mira antes qué tiene con my_draft y pregunta a la persona. / Required true; the draft is lost for good."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. The draft is lost and cannot be recovered: look first at what it holds with my_draft and ask the person."
    • changedOutput schema / properties / deleted / description
      Previous value: -"Se ha borrado de verdad en esta llamada."New value: +"It really was deleted in this call."
    • changedOutput schema / properties / hadDraft / description
      Previous value: -"Había un borrador antes de la llamada."New value: +"There was a draft before this call."
    • changedOutput schema / properties / note / description
      Previous value: -"Qué se ha perdido exactamente, en una frase."New value: +"Exactly what has been lost, in one sentence."
    • changedOutput schema / properties / ok / description
      Previous value: -"Siempre true: no queda borrador guardado."New value: +"Always true: no draft is left saved."
    • changedOutput schema / properties / wasEditing / description
      Previous value: -"Slug que editaba el borrador borrado, o null si era de plantilla nueva."New value: +"Slug the deleted draft was editing, or null if it was for a new template."
  3. First observed

TDQS

A4.5/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: it discloses that the operation is irreversible, requires confirm=true, affects the single account-level draft, and has elevated risk for EDIT drafts. This is exactly the destructive-operation context an agent needs before calling.

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 critical fact and the confirm gate are front-loaded, which is good, but the phrasing is run-on and the closing sentence ('It is what lets you start another one with create_draft without going through the website') is vague and adds little operational value.

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?

An output schema exists, so return values need not be described. The description covers the destructive nature, the confirmation requirement, the pre-check workflow, and the sibling hand-offs, leaving nothing an agent needs in order to call this safely.

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 the single parameter's description already explains that confirm must be true and that the draft is unrecoverable. The description reinforces rather than extends this, so it earns the baseline 3 rather than more.

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 (DELETES) and resource (the saved publish draft), plus the cardinality constraint 'there is ONE per account'. This clearly distinguishes it from sibling write tools like create_draft, update_draft, and the read-only my_draft.

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 names the alternatives and when to use them: check contents via my_draft and ask the person before deleting, with extra caution for EDIT drafts that represent pending changes to a published template. It also notes the follow-on path (create_draft) rather than website deletion.

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