Skip to main content
Glama

delete_style

Destructive

Permanently deletes one of the person's own styles, which cannot be undone; built-in styles are protected. Requires confirm: true, otherwise it only reports what would be removed.

Instructions

Delete one of the person's own styles for good. It can't be undone, and templates in that style stop opening. Without confirm: true it only says what will go; ask the person first. Dinoctor reloads afterwards. Built-in styles can't be deleted. To only stop using it, switch with use_style instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "delete_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe person's own style id from my_styles (built-in styles can't be used here).
confirmNotrue only after the person said to delete it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / confirm / description
      Added value: +"true only after the person said to delete it."
    • addedInput schema / properties / id / description
      Added value: +"The person's own style id from my_styles (built-in styles can't be used here)."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds the consequences an agent cannot infer: irreversibility, that templates in that style stop opening, the dry-run preview when confirm is absent, and a post-delete reload. This is exactly the behavioral context annotations alone cannot 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?

Sentences are short, front-loaded with the destructive consequence, then the confirm gate, then exclusions and the alternative. Minor deduction for "Dinoctor reloads afterwards," which is terse enough to be ambiguous about what reloads and why it matters.

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 two-parameter destructive tool with no output schema, the description covers consequence, consent requirement, dry-run behavior, eligibility limits, and the safer alternative. Nothing an agent needs to call it responsibly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description goes further by explaining what omitting confirm actually does (a preview rather than a delete) and by tying confirm to obtaining the person's consent. The id parameter's provenance is already fully covered by the schema, so no further gain there.

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?

"Delete one of the person's own styles for good" names a specific verb, resource, and ownership scope, and immediately distinguishes itself from use_style for the non-destructive case. An agent can tell this apart from sibling style tools without opening the 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?

It explicitly states the confirm gate ("Without confirm: true it only says what will go; ask the person first"), the exclusion ("Built-in styles can't be deleted"), and the alternative ("To only stop using it, switch with use_style instead"). Both when-to-use and when-not-to-use are covered.

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