character-forge-mcp

Overview Schema Source Related Servers Discussions Admin

Generation prompt brief (on request)

character_prompt

Read-only

Returns the rules and card material needed to write one generation prompt for a saved character — concept, illustration, voice, video, song, or theme — ready to save.

Instructions

ONLY when the user asks for a specific prompt. Returns the rules and card material for writing ONE generation prompt for a saved character — concept, illustration, voice, video, song or theme. Write it, then call character_prompt_save. Prompts only; no generator is called. Never run this as part of creating a character.

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": {
      "id": "<id>",
      "kind": "<kind>"
    },
    "name": "character_prompt"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Character id.
`kind`	Yes	concept = T-pose sheet · illustration = key-art scene · voice = TTS voice design · video = Seedance-style clip · song = Suno · theme = instrumental leitmotif (ElevenLabs Music composition plan)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds that it returns rule and card material rather than executing anything ('no generator is called') and that it must be followed by a save call. What it omits is the shape/size of the returned material, which matters for a tool with no output schema, but the behavioral footprint is otherwise well disclosed.

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?

Front-loads the gating condition and the core purpose, then the sequencing rule, in three tight sentences. Minor redundancy between 'Returns the rules and card material' and 'Prompts only; no generator is called', but nothing is filler.

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

Completeness4/5

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

With only two fully documented parameters, a readOnly annotation, and no output schema, the description covers purpose, gating, and the required follow-up call. The one remaining gap is that it doesn't characterize what the returned rule/card material contains, which an agent might want before invoking.

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 coverage is 100% and the enum description already spells out each kind in detail (T-pose sheet, key-art scene, TTS voice design, etc.), so the description's list of kinds largely duplicates structured data. No additional syntax or constraint guidance is offered beyond the schema, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource: 'Returns the rules and card material for writing ONE generation prompt for a saved character', then enumerates the six prompt kinds. It also names the follow-on sibling (character_prompt_save), so an agent can place it precisely in the workflow without opening another schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('ONLY when the user asks for a specific prompt'), an explicit exclusion ('Never run this as part of creating a character'), and the required next action ('Write it, then call character_prompt_save'). When-to-use, when-not-to-use, and the alternative path are all present.

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