Skip to main content
Glama
story-architect-mcp

story-architect-mcp

by PTCuong-1102

Generate Optimized Writing Prompt

story_generate_writing_prompt

Generates a refined system prompt for the next writing turn by combining the previous chapter, outline, lore, style guide, and Chekhov guns. Use it to keep AI novel writing consistent.

Instructions

Đọc chương trước + Dàn ý + Lore + Style Guide + Chekhov Guns → Tạo System Prompt gọt giũa hoàn hảo cho lượt viết tiếp theo.

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": {
      "arc": "<arc>",
      "chapter": "<chapter>"
    },
    "name": "story_generate_writing_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
arcYesArc ID (ví dụ: arc_01)
chapterYesChapter ID (ví dụ: ch_003)
strategyNoChiến lược viết: continue (viết tiếp), rewrite (viết lại), expand (mở rộng)continue

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.7.0
    • addedInput schema / properties / arc / maxLength
      Added value: +64
    • addedInput schema / properties / arc / minLength
      Added value: +1
    • addedInput schema / properties / chapter / maxLength
      Added value: +64
    • addedInput schema / properties / chapter / minLength
      Added value: +1
  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 must carry the behavioral load. It usefully discloses the input sources it reads (previous chapter, outline, lore, style guide, Chekhov guns), which is real context beyond the schema, but it is silent on whether it mutates state, whether it persists the generated prompt, how large or structured the output is, and what happens if those sources are missing.

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?

A single compact sentence using an arrow to front-load inputs and the result; zero filler. It would be stronger if the disambiguating use case came before the input list. Note the description is in Vietnamese while the tool name, title, and schema wording are mixed, which slightly hurts scanability for an agent working in English.

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 3-parameter, 100%-documented tool with no output schema and no annotations, the description covers the 'what goes in → what comes out' contract but leaves the output shape, whether it is returned or stored, and failure modes unspecified. Adequate but with clear gaps for a tool whose whole value is the generated artifact.

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 arc, chapter, and the strategy enum in full, making 3 the baseline. The description adds nothing about parameters — notably the strategy enum is never referenced, so the agent gets no narrative hint that 'rewrite' vs 'expand' changes what context is gathered.

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?

States a concrete verb ('Tạo' / create) and a concrete artifact ('System Prompt') from a named set of inputs, so the agent knows this aggregates story context rather than writing prose itself. It does not name or contrast with the closest sibling (story_write_chapter), which would be the natural alternative an agent might confuse it with.

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?

The phrase 'cho lượt viết tiếp theo' (for the next writing turn) implies when to use it, but there is no explicit when-not, no mention of why one would choose this over story_write_chapter or story_query_context, and no stated prerequisites such as an existing arc/chapter.

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