Skip to main content
Glama
Sign In
character-forge-mcp

character-forge-mcp

by gdhub-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Keep the tournament winner

character_pick

Finalize a judged character variant: move the winner from drafts to the library, delete the other variants in its group, and store the verdict and selected concept image.

Instructions

After the judge's verdict: moves the winning variant from the drafts into the library and deletes the other variants of its group (losers are not kept). If the character was started from the user's own concept image (meta.concept_image), it becomes the winner's concept. Write meta.verdict into the winner first.

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": {
      "winner": "<winner>"
    },
    "name": "character_pick"
  }
}

Input Schema

NameRequiredDescriptionDefault
winnerYesId of the winning variant.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.2/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 does well: it discloses that losers are deleted (not merely unselected), that the group's other variants are destroyed, and that the concept image may be replaced. It stops short of stating reversibility/confirmation, permissions, or error behavior for an invalid winner id.

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-loaded with the precondition, then the primary effect, then the secondary caveats. Dense but every sentence carries information; only the trailing prerequisite sentence would read better placed before the mutation description.

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

Completeness5/5

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

For a one-parameter, destructive, no-output-schema tool, the description covers prerequisite state, the promotion, the deletion, and the concept-image side effect. There is no output schema to explain, and the remaining gaps are minor for this complexity.

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 single parameter is already documented ('Id of the winning variant'), so the description adds little beyond restating that the winner is the surviving variant. The mentions of meta.concept_image and meta.verdict describe side effects, not the input parameter.

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 pair: moves the winning variant from drafts into the library and deletes the other variants in its group. The tournament/verdict framing makes it unambiguous which operation this is relative to generic create/save siblings.

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

Usage Guidelines4/5

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

Gives a clear precondition ('After the judge's verdict') and an ordering rule ('Write meta.verdict into the winner first'), which tells the agent when this tool is appropriate. It does not, however, name an alternative or explicitly state when not to call it.

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