Skip to main content
Glama
PTCuong-1102

story-architect-mcp

by PTCuong-1102
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Detect Timeline Conflicts & Generate Mermaid Parallel Timeline

story_detect_timeline_conflicts

Detects timeline conflicts by analyzing dates, events, locations, and characters across parallel storylines, then exports a Mermaid chart to visualize issues.

Instructions

Phân tích các mốc thời gian tuyệt đối & tương đối, sự kiện, địa điểm và nhân vật để phát hiện mâu thuẫn timeline (như phân thân xuất hiện ở 2 nơi cùng lúc, đảo ngược thứ tự sự kiện). Hỗ trợ các tuyến truyện song song (Threads/Subplots) và xuất biểu đồ Mermaid trực quan.

Input Schema

NameRequiredDescriptionDefault
addEventNoThêm sự kiện timeline mới (nếu cần)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.7.0
    • addedInput schema / properties / addEvent / properties / absoluteDate
      Added value: +{
+  "description": "Mốc thời gian tuyệt đối (YYYY-MM-DD hoặc in-world date)",
+  "type": "string"
+}
    • addedInput schema / properties / addEvent / properties / characters
      Added value: +{
+  "description": "Danh sách nhân vật tham gia",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / addEvent / properties / label / maxLength
      Added value: +300
    • addedInput schema / properties / addEvent / properties / label / minLength
      Added value: +1
    • addedInput schema / properties / addEvent / properties / location
      Added value: +{
+  "description": "Địa điểm diễn ra sự kiện",
+  "type": "string"
+}
    • addedInput schema / properties / addEvent / properties / relativeOrder / description
      Added value: +"Thứ tự tương đối của sự kiện"
    • addedInput schema / properties / addEvent / properties / thread
      Added value: +{
+  "description": "Tuyến subplot / storyline (ví dụ: \"Phe Kháng Chiến\", \"Cung Đình\")",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It frames the tool as a read/analysis operation ('phân tích ... để phát hiện mâu thuẫn') yet the schema exposes an addEvent capability, meaning the tool can mutate timeline state — and the description never says so, nor whether conflicts are persisted, what permissions are needed, or how results are returned beyond 'exports a Mermaid chart'.

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 dense sentences with the detection purpose front-loaded followed by the parallel-thread/Mermaid output capability. No filler, though the visual-output claim sits in the same breath as analysis without separating the two modes of operation.

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 tool with no annotations and no output schema, the description covers the analysis purpose and the Mermaid return artifact reasonably well. But it omits the event-insertion behavior implied by addEvent and says nothing about what the conflict report itself contains, leaving a mutation-capable tool under-described.

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 every sub-field (label, thread, chapter, location, characters, absoluteDate, relativeOrder) is already documented in the schema; baseline 3 applies. The description adds only the thematic link to 'Threads/Subplots' for the thread field and never mentions the single top-level addEvent parameter, so it contributes little beyond structured data.

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 specific verb and resource: analyze absolute/relative time markers, events, locations and characters to detect timeline contradictions, with concrete examples (a character in two places at once, reversed event order) plus Mermaid diagram output. The scope is unmistakable and no sibling tool overlaps with conflict detection, though it does not explicitly name non-overlap.

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?

Usage is only implied: an agent can infer this is for consistency-checking a story's chronology, but the description gives no trigger conditions, no prerequisites, and no when-not-to-use guidance versus other analysis siblings such as story_log_plot_hole or story_analyze_pacing.

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