Lunafic

Create world

create_world

Create a new world as a draft. worldKind 'private' is for your own writing, 'playable' is built for players. Publish it afterwards with update_world.

Input Schema

Name	Required	Description
`hook`	No
`rules`	No
`title`	Yes
`genres`	No	Up to 3 genres from the fixed 22-genre taxonomy.
`maturity`	No
`prologue`	No	The prologue: the opening players read first, on the world page and before they play, written like the first page of a novel. Plain paragraphs separated by a blank line, 400 to 4000 characters. Say who the player is (write {{player}} for the player's character, never a role's name), where they are, who is there (each name with one plain description), and what is going on, then stop right before the first move. Explain every made-up word the first time it appears. Only facts the wiki already holds. Required to publish.
`synopsis`	No
`formality`	No
`worldKind`	No
`derivation`	No
`authoringMode`	No
`dialogueFormat`	No
`targetAudience`	No
`characterLanguage`	No
`narrativeLanguage`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedInput schema / properties / prologue / description

Previous value: -"The prologue: the opening players read first, on the world page and before they play, written like the first page of a novel. Plain paragraphs separated by a blank line, 400 to 4000 characters. Say who the player is, where they are, who is there (each name with one plain description), and what is going on, then stop right before the first move. Explain every made-up word the first time it appears. Only facts the wiki already holds. Required to publish."New value: +"The prologue: the opening players read first, on the world page and before they play, written like the first page of a novel. Plain paragraphs separated by a blank line, 400 to 4000 characters. Say who the player is (write {{player}} for the player's character, never a role's name), where they are, who is there (each name with one plain description), and what is going on, then stop right before the first move. Explain every made-up word the first time it appears. Only facts the wiki already holds. Required to publish."

Changed1 schema field changedOct 21, 2026

addedInput schema / properties / prologue

Added value: +{
+  "description": "The prologue: the opening players read first, on the world page and before they play, written like the first page of a novel. Plain paragraphs separated by a blank line, 400 to 4000 characters. Say who the player is, where they are, who is there (each name with one plain description), and what is going on, then stop right before the first move. Explain every made-up word the first time it appears. Only facts the wiki already holds. Required to publish.",
+  "type": "string"
+}

First observedOct 15, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations cover the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description's real contribution is disclosing that creation produces a non-published draft that requires a separate publish step. That is useful behavioral context an agent cannot infer from structured fields. It does not say what the call returns or whether repeated calls create duplicates.

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?

Three short sentences, front-loaded with the action and draft state, followed by the parameter hint and the publish route. Nothing is padded or restated from the title.

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

Completeness2/5

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

For a 15-parameter creation tool with no output schema, the description never says what comes back (e.g. a world identifier), which fields besides title are needed to publish, or what the maturity/format enums mean. Only the worldKind and publish-path gaps are addressed, leaving most of the call surface undocumented.

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

Parameters2/5

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

Schema description coverage is only 13% across 15 parameters, so the description must carry most of the semantic load, yet it explains only worldKind. Opaque enums such as authoringMode ('mc' vs 'author'), derivation, and dialogueFormat are left unexplained in both schema and description.

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 ('Create a new world') plus the resulting state ('as a draft'), which is materially different from sibling update_world. It does not differentiate itself from create_entry, but the resource is unambiguous.

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?

Explains the choice between the two worldKind values ('private' for your own writing vs 'playable' for players) and names the follow-up tool and action ('Publish it afterwards with update_world'). No when-not guidance or prerequisites, but the routing is clear.

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

All Lunafic tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?