World edit schema
world_schemaThe ops world_apply accepts (add_zone, add_npc, add_quest, add_link, set_worldgen and the rest), each with its fields as JSON Schema: types, bounds, the closed lists of words and which keys are required. Printed from the same table the engine validates against, so it cannot drift from what is accepted. Pass op to get one op's schema alone. Costs no units.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "world_schema"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| op | No | One op's name (add_zone, add_npc, add_quest and the rest) to get only that op's schema; omit it for all of them. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ms | No | Milliseconds the run took. | |
| job | Yes | The job id; the job tool reads it. | |
| verb | No | The tool that made it. | |
| files | No | Files made, each with a name, type, size and a signed URL. | |
| units | No | Units this call cost. | |
| result | No | The engine's own answer, a JSON document. | |
| status | No | queued when the job runs in the background. |