Skip to main content
Glama
PTCuong-1102

story-architect-mcp

by PTCuong-1102
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Map Character Relationships Graph

story_map_relationships

Analyzes manuscripts to map and update character relationships in .story/relationships.json, auto-detecting co-occurring pairs and labeling links extracted or inferred.

Instructions

Phân tích bản thảo và tự động cập nhật Đồ thị quan hệ nhân vật vào .story/relationships.json. Nếu bỏ trống source/target sẽ tự quét toàn bộ manuscript để phát hiện các cặp nhân vật đồng xuất hiện. Mỗi quan hệ mang nhãn nguồn gốc: EXTRACTED (người khẳng định) hoặc INFERRED (máy suy ra).

Input Schema

NameRequiredDescriptionDefault
typeNoLoại mối quan hệ
sourceNoNhân vật A (bỏ trống để chạy chế độ tự quét)
targetNoNhân vật B (bỏ trống để chạy chế độ tự quét)
chapterNoChương diễn ra biến động quan hệ
descriptionNoMô tả mối quan hệ
minChaptersNoNgưỡng số chương đồng xuất hiện (chế độ tự quét)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.7.0
    • addedInput schema / properties / minChapters
      Added value: +{
+  "default": 2,
+  "description": "Ngưỡng số chương đồng xuất hiện (chế độ tự quét)",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / source / description
      Previous value: -"Nhân vật A"New value: +"Nhân vật A (bỏ trống để chạy chế độ tự quét)"
    • changedInput schema / properties / target / description
      Previous value: -"Nhân vật B"New value: +"Nhân vật B (bỏ trống để chạy chế độ tự quét)"
    • removedInput schema / required
      Removed value: -[
-  "source",
-  "target",
-  "type"
-]
  2. First observedv0.1.0

TDQS

A3.6/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 it discloses the key trait that this tool writes/updates a persistent file (.story/relationships.json), plus the auto-scan trigger and the EXTRACTED/INFERRED provenance labeling. It leaves out whether existing relationships are overwritten or merged, permission needs, and reversibility, keeping it from a 5.

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 compact sentences, front-loaded with the core action and destination file, then mode behavior, then the provenance vocabulary. No filler, though the provenance-label sentence is somewhat tangential to invocation.

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 6-parameter, no-required, mutation-style tool with no annotations and no output schema, the description covers modes and labeling but omits what the tool returns and whether an existing relationships.json is replaced or merged—material gaps an agent would want before calling it.

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 every parameter including the blank-source/target auto-scan behavior and minChapters. The description largely restates those points and adds little new syntax or format meaning, 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?

States a specific verb+resource: analyzes the manuscript and auto-updates a character-relationship graph persisted to .story/relationships.json. This clearly distinguishes it from most siblings, though it does not explicitly differentiate from the related story_track_character_state or story_extract_entities_to_bible tools.

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?

Explains the two operating modes (targeted pair when source/target are supplied vs. full-manuscript auto-scan when they are blank) and the minChapters threshold, which is real mode-selection guidance. However, it gives no when-not-to-use guidance and never routes the agent to or away from sibling tools like story_track_character_state.

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