Skip to main content
Glama
PTCuong-1102

story-architect-mcp

by PTCuong-1102
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set Story Project Path

story_set_project

Set or switch the target novel project while automatically rejecting code projects to avoid resource waste. Use force=true to bypass detection.

Instructions

Thiết lập hoặc chuyển đổi dự án tiểu thuyết đích. Tự động phát hiện và từ chối dự án code (Node.js, Python, Rust, v.v.) để tránh lãng phí tài nguyên. Dùng force=true để bỏ qua kiểm tra.

Input Schema

NameRequiredDescriptionDefault
forceNoBỏ qua kiểm tra loại dự án (dùng khi muốn khởi tạo dự án mới trong thư mục bất kỳ)
projectPathYesĐường dẫn đến thư mục dự án tiểu thuyết (tuyệt đối hoặc tương đối so với cwd)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.0
    • addedInput schema / properties / force
      Added value: +{
+  "default": false,
+  "description": "Bỏ qua kiểm tra loại dự án (dùng khi muốn khởi tạo dự án mới trong thư mục bất kỳ)",
+  "type": "boolean"
+}
    • addedInput schema / properties / projectPath / minLength
      Added value: +1
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description usefully discloses a non-obvious behavior: automatic detection and rejection of code projects (Node.js, Python, Rust) to avoid wasted resources, plus the force escape hatch. It omits what the failure response looks like and whether the setting persists to config, so the mutation's side effects remain partially undisclosed.

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?

Three short sentences, front-loaded with the core action before the validation caveat. The force sentence slightly duplicates the schema field description, keeping it just short of a 5.

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

Completeness4/5

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

For a simple two-parameter tool with full schema coverage and no output schema, the description covers purpose, the validation trap, and the override. Only the return/error semantics on rejection are missing, which is a minor gap.

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 both parameters are already documented, including force's meaning ('Bỏ qua kiểm tra loại dự án'). The description essentially restates the schema's force semantics rather than adding new detail, so the baseline 3 applies.

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 and resource ('Thiết lập hoặc chuyển đổi dự án tiểu thuyết đích' – set/switch the target novel project), which is concrete. It does not explicitly name the contrasting siblings (story_init, story_list_projects, story_get_project_info), so differentiation is implied rather than stated.

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 one actionable condition ('Dùng force=true để bỏ qua kiểm tra' – use force to skip the check), which tells the agent when to override validation. However, it never says when to use this tool versus story_init or story_list_projects, leaving the primary routing decision to inference.

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