Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

delete_draft

DELETES the saved publish draft (there is ONE per account). It requires confirmar=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
confirmNoRequired true. The draft is lost and cannot be recovered: look first at what it holds with my_draft and ask the person.
confirmarNoDEPRECATED 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.

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

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well: it states that the operation is destructive, cannot be undone, requires confirmation, and that drafts are one per account. It also flags the sensitive edit-draft case, which is exactly the behavioral context an agent needs.

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 three tight sentences with no filler: the action and one-per-account fact are front-loaded, followed by irreversibility, user confirmation guidance, and the create_draft relationship. Every sentence earns its place.

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 destructive mutation tool, the description is complete: it covers what gets deleted, the single-draft constraint, confirmation requirements, irreversibility, and the appropriate pre-check workflow with my_draft. Since an output schema exists, return-value details are not needed.

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 the schema already documents the confirm/confirmar parameters in detail. The description reinforces that confirmation is required and irreversible, but adds little semantic value beyond what the schema provides.

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 states a specific verb and resource: it DELETES the saved publish draft, and clarifies the one-per-account constraint. This lets an agent clearly distinguish deletion from related operations like create_draft, update_draft, or 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?

The description explicitly instructs the agent to show the draft with my_draft and ask the user before deleting, especially for EDIT drafts. It also explains the relationship to create_draft, giving clear when-and-how guidance and naming the relevant sibling tools.

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