Skip to main content
Glama

novel_delete_book

Delete or clean up a book's files by previewing, moving selected parts to trash, restoring from trash, or permanently purging them without affecting global settings or logs.

Instructions

按书删/清(含回收站):默认preview预览;apply移入回收站(keys选部分);restore恢复;purge彻底删。不动全局/设置/日志。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
bookNo书名
keysNo只清指定targets[].key(apply)
rootNo书库根
actionNo操作
trashIdNo回收站id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv8.0.0
    • changedInput schema / properties / action / description
      Previous value: -"preview=预览将清理的内容(默认,不写盘);apply=执行删除(移入回收站);list=列出回收站条目;restore=从回收站恢复(需 trashId);purge=彻底删除某个回收站条目(需 trashId,不可恢复)。"New value: +"操作"
    • changedInput schema / properties / book / description
      Previous value: -"书名(与 novels/ 下的目录名一致;preview/apply 必填)。"New value: +"书名"
    • changedInput schema / properties / keys / description
      Previous value: -"可选。只清理这些位置(取自 preview 返回的 targets[].key,例如只清 data:audits 与 data:style-reports 就是「只删报告历史」)。省略=全选,即删整本书。apply 时生效。"New value: +"只清指定targets[].key(apply)"
    • changedInput schema / properties / keys / items / description
      Previous value: -"位置 key(chapters/creation/data:<子目录>/legacy/profile)"New value: +"key"
    • changedInput schema / properties / root / description
      Previous value: -"章节库根目录(含 novels 子目录)。"New value: +"书库根"
    • changedInput schema / properties / trashId / description
      Previous value: -"回收站条目 id(restore/purge 必填,取自 preview/apply 返回的 trashId 或 action=list)。"New value: +"回收站id"
  2. Addedv6.9.0

TDQS

A4/5.0
Behavior4/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 disclose the destructive gradient: preview is non-destructive, apply is recoverable (moves to trash), purge is permanent, and the blast radius is limited to one book plus global/settings/logs being untouched. It does not cover permissions, confirmation requirements, or what a preview returns.

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?

Two dense telegraphic clauses with the destructive defaults and the mode list front-loaded and zero filler. Every phrase carries information an agent needs before calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the dangerous behavior well for a 5-parameter, zero-required, no-annotation, no-output-schema mutation tool. However, the 'list' action in the enum is never explained, and with no output schema the description should say what preview returns, since that is the entry point for every safe call.

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 already 100%, so the baseline is 3, but the description adds real meaning by coupling parameters to modes: keys only applies during apply, restore/purge operate on trash entries. trashId and the root parameter remain unexplained beyond their schema labels, and the 'list' action is never tied to how a trashId is obtained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a concrete verb and resource (delete/clean by book, trash included) and states the negative scope: it does not touch global/settings/logs. That scope line separates it from novel_settings and the other novel_* tools, though no sibling is named explicitly.

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?

Spells out the mode ladder: preview by default, apply moves to trash, keys restricts apply to a subset, restore and purge for trash entries. It gives no explicit 'use this instead of X' routing, but the default-is-preview default is clearly stated so the agent knows a no-arg call is safe.

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