character-forge-mcp

Overview Schema Source Related Servers Discussions Admin

Record a character's turn (experimental)

character_meet_turn

Records a character's turn in a scene, then returns the next speaker's packet or the finished scene to continue multi-character dialogue.

Instructions

Records one character's turn in a scene started by character_meet, exactly as the character returned it. Returns the next speaker and their packet, or the finished scene.

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": {
      "scene": "<scene>",
      "speaker": "<speaker>",
      "turn": "<turn>"
    },
    "name": "character_meet_turn"
  }
}

Input Schema

Name	Required	Description
`turn`	Yes
`scene`	Yes	Scene id from character_meet.
`speaker`	Yes	Id of the character whose turn this is.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.3.3Nov 14, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the turn is recorded exactly as returned and that the result is either the next speaker with their packet or the finished scene, but it does not describe mutation side effects, validation failures, or whether repeated calls are idempotent.

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

Conciseness5/5

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

Two short sentences with no waste. The core action and the return behavior are front-loaded, and the reference to character_meet establishes sequence immediately.

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?

The tool has a complex nested input schema, no output schema, and no annotations. The description covers the essential call sequence and return shape, but it leaves out error behavior, ordering guarantees, and any explanation of what the next speaker's packet contains.

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 67%, so the schema already explains most parameters. The description adds that the scene must come from character_meet and that the speaker is the character whose turn it is, plus the instruction to pass the turn exactly as returned, but it does not add much detail about the nested turn packet beyond the schema.

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: records one character's turn in a scene started by character_meet. This clearly distinguishes it from the scene-starting sibling, though it does not differentiate from character_meet_event.

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 description implies the turn-taking workflow by requiring a scene from character_meet and by returning the next speaker or finished scene. It does not explicitly say when not to use it or how it relates to character_meet_event.

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