Skip to main content
Glama

mark_character_dead

Records a character as deceased in a given chapter with a specified cause, ensuring narrative continuity across the multi-agent book writing pipeline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
character_nameYes
chapterYes
causeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core handler function that marks a character as dead by updating the continuity log and saving the project.
    def mark_character_dead(character_name: str, chapter: int, cause: str) -> str:
        _, cont = require_project()
        cont.mark_dead(character_name, chapter, cause)
        save_project_and_continuity()
        return f"{character_name} marked dead."
  • FastMCP tool registration for mark_character_dead, exposing it as an MCP tool and delegating to the workflow handler.
    @mcp.tool()
    async def mark_character_dead(character_name: str, chapter: int, cause: str) -> str:
        try:
            return workflow.mark_character_dead(character_name, chapter, cause)
        except ValueError as e:
            return str(e)
  • Model method on ContinuityLog that sets the character's status to DEAD and records death chapter and cause.
    def mark_dead(self, name: str, chapter: int, cause: str) -> None:
        char = self.get_character(name)
        if char:
            char.status = CharacterStatus.DEAD
            char.death_chapter = chapter
            char.death_cause = cause
  • CharacterState dataclass with fields for death_chapter and death_cause used by mark_dead.
    class CharacterState:
        name: str
        status: CharacterStatus = CharacterStatus.ALIVE
        death_chapter: int | None = None
        death_cause: str = ""
        items: list[str] = field(default_factory=list)
  • Enum defining CharacterStatus with DEAD value used when marking a character as dead.
    class CharacterStatus(str, Enum):
        ALIVE = "alive"
        DEAD = "dead"
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BurgersJackson/storywright-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server