Skip to main content
Glama
Sign In
worldanvil-mcp-server

worldanvil-mcp-server

by daireb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Export entire world to disk

export_world

Export a World Anvil world as local JSON files for backup or migration, including articles, images, maps, timelines, and secrets.

Instructions

Clone a COMPLETE world to a local directory as raw full-granularity JSON — articles, categories, secrets, map hierarchies (layers/groups/markers), timelines, histories, notebooks+notes, subscriber groups, world meta — plus downloaded image binaries and an entities.json id→{title,slug,file} index for rewriting @mention links during migration. Makes hundreds of API calls; takes minutes on a large world. Returns a summary; data goes to disk, NOT into context — read specific exported files afterwards if needed. Refuses to write into a non-empty directory that isn't a previous export. Requires an absolute output path.

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>",
      "output_dir": "<output_dir>"
    },
    "name": "export_world"
  }
}

Input Schema

NameRequiredDescriptionDefault
world_idYesUUID of the world to export
output_dirYesAbsolute path of the directory to export into (created if missing)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does an excellent job: it discloses that the tool makes hundreds of API calls, takes minutes, returns only a summary, writes data to disk rather than context, refuses to write into non-empty non-export directories, and requires an absolute output path. This is thorough behavioral disclosure.

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?

The description is somewhat long with a large list of included entities, but every sentence provides valuable information. It is front-loaded with the core purpose and structured logically (what, how long, return behavior, constraints). A slight trimming could improve conciseness, but it remains efficient for the tool's complexity.

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 complex tool with no output schema and no annotations, the description covers all critical aspects: full content list, side effects (disk writes, downloads), performance (minutes), return behavior, and special conditions (empty dir, absolute path). The user/agent has enough to invoke and handle the tool correctly.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds meaningful parameter context beyond the schema: output_dir must be absolute, is created if missing, and must be empty or a previous export. It also clarifies world_id is a UUID. This enriches the schema definitions.

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 clearly states the tool clones a COMPLETE world to a local directory as raw full-granularity JSON, listing all included data types (articles, categories, secrets, etc.). It uses a specific verb ('Clone'/export) and resource ('world'), and it is clearly distinct from sibling tools like get_world or list_articles. No ambiguity.

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?

The description provides clear context for when to use the tool (full migration, rewriting @mention links) and includes important usage caveats (data goes to disk, not into context; read specific exported files afterwards). However, it does not explicitly mention alternatives or when NOT to use this tool, though no sibling tool serves the same purpose.

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