worldanvil-mcp-server

Create category

create_category

Create a category or subcategory in a World Anvil world, using a world ID and title, with optional parent ID for nesting.

Instructions

Create a category (folder) in a world, optionally nested under a parent category.

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": {
      "world_id": "<world_id>",
      "title": "<title>"
    },
    "name": "create_category"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Category name
`world_id`	Yes	UUID of the world
`parent_id`	No	UUID of parent category for nesting
`extra_fields`	No	Advanced: extra raw API fields (e.g. description, icon).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 3, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It states 'create' which implies mutation, but does not mention permissions, side effects, reversibility, error behavior, or what the API returns. This leaves significant gaps for a write operation.

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?

The description is a single, efficient sentence that front-loads the core action and then adds the key optional nuance. No filler or redundant content.

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?

With no output schema and no annotations, the description should cover more context. It clearly states the purpose and optional nesting, but does not explain return values, error conditions, or prerequisites (e.g., world existence). This is adequate for a simple tool but leaves notable gaps for an agent to fully predict behavior.

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 100%, with each parameter having a clear description. The tool description adds marginal value by clarifying 'folder' and optional nesting, but does not enhance understanding of parameter formats, constraints, or the purpose of extra_fields beyond what the schema already provides.

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?

The description uses the specific verb 'create' with the resource 'category (folder)' and clarifies it operates 'in a world' with optional nesting under a parent. This clearly distinguishes it from sibling tools like list_categories, update_category, and delete_category.

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 tool is for creating categories but does not explicitly state when to use it over alternatives or any prerequisites. It mentions optional nesting but provides no guidance on when to use create_category vs other category-related tools or what to check beforehand.

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

Deploy Server