Skip to main content
Glama
PTCuong-1102

story-architect-mcp

by PTCuong-1102
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Auto Refactor Novel Structure

story_auto_refactor_structure

Refactors and normalizes novel project directories into a standard layout, with a dry-run preview before applying changes.

Instructions

Phân loại và chuẩn hóa cấu trúc thư mục dự án tiểu thuyết theo layout chuẩn. Hỗ trợ dry-run mode (confirm=false) để preview trước khi thực hiện.

Input Schema

NameRequiredDescriptionDefault
confirmNofalse = dry-run (chỉ preview), true = thực hiện thực sự (sẽ tự động snapshot trước)
strategyNoChiến lược sắp xếp: auto_profile (mặc định, v0.6.0) — nhận diện bố cục hiện có trước: một file lớn chứa nhiều chương → TÁCH theo tiêu đề chương; thư mục phân tập tự đặt tên → map thành arc_XX; chương phẳng → đánh số lại ch_XXX by_chapter — mọi file bản thảo → manuscript/arc_01/ by_arc — đoán arc từ tên file/nội dung ("quyển 3", "part 2"...) chronological — đánh số theo thời gian sửa fileauto_profile
projectPathYesĐường dẫn dự án

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.7.0
    • addedInput schema / properties / projectPath / minLength
      Added value: +1
    • changedInput schema / properties / strategy / default
      Previous value: -"by_chapter"New value: +"auto_profile"
    • changedInput schema / properties / strategy / description
      Previous value: -"Chiến lược sắp xếp"New value: +"Chiến lược sắp xếp:\n  auto_profile (mặc định, v0.6.0) — nhận diện bố cục hiện có trước: một file lớn chứa nhiều chương → TÁCH theo tiêu đề chương; thư mục phân tập tự đặt tên → map thành arc_XX; chương phẳng → đánh số lại ch_XXX\n  by_chapter — mọi file bản thảo → manuscript/arc_01/\n  by_arc — đoán arc từ tên file/nội dung (\"quyển 3\", \"part 2\"...)\n  chronological — đánh số theo thời gian sửa file"
    • changedInput schema / properties / strategy / enum
      Previous value: -[
-  "by_chapter",
-  "by_arc",
-  "chronological"
-]New value: +[
+  "auto_profile",
+  "by_chapter",
+  "by_arc",
+  "chronological"
+]
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of disclosing behavior. It does explain the dry-run safety path, which is valuable, but for a file-moving mutation it omits whether the operation is reversible, that a snapshot happens (that detail lives only in the schema), and what the result looks like. It signals the operation but not its consequences.

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?

Two tight sentences with the core purpose front-loaded and the safety mode immediately following. Nothing is wasted, though the dry-run sentence could have carried more behavioral detail given the space available.

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?

For a mutation tool with no annotations and no output schema, the description is minimal: it lacks any mention of what is returned, whether snapshot/rollback protects the user, or how it relates to the scan/verdict tools. The dry-run hint helps but does not fully cover the complexity of a directory-restructuring operation.

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%, with the strategy enum fully documented in-schema. The description's mention of confirm=false as dry-run duplicates what the schema already states, adding no new semantics. Baseline 3 is appropriate given the schema does the heavy lifting.

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?

The description states a specific verb+resource: it classifies and normalizes the directory structure of a novel project into a standard layout. This clearly distinguishes it from read-only siblings like story_scan_messy_project, though it does not explicitly name the related story_apply_layout_verdict. An agent can identify the operation without reading 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives useful procedural guidance: use dry-run mode (confirm=false) to preview before committing. However, it never states when this tool should be chosen over closely related siblings such as story_scan_messy_project or story_apply_layout_verdict, nor does it state prerequisites. Usage is implied rather than fully directed.

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

Deploy Server

Other Tools