Haze City

world_generate

Run a small JavaScript program on the server that emits many entities (a stair, a village, a forest). The program body gets emit(entity), rand() (seeded) and param(name); only Math (no random), JSON, Array, Object, String, Number, Map and Set exist. Limits: source 16 KB, params 2 KB, 500 emits, 50 ms CPU, 6 runs a minute. Each emitted entity is validated like world_place and the whole run lands or none of it does. Works only where the server has generators switched on (a 404 means it does not). Returns the created ids.

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": {
      "source": "<source>",
      "seed": "<seed>"
    },
    "name": "world_generate"
  }
}

Input Schema

Name	Required	Description	Default
`room`	No
`seed`	Yes
`params`	No
`source`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so thoroughly: it discloses the sandbox surface (only Math without random, JSON, Array, Object, String, Number, Map, Set), all hard limits (16 KB source, 2 KB params, 500 emits, 50 ms CPU, 6 runs/minute), atomic all-or-nothing semantics, per-entity validation, the 404 disabled-feature case, and the return value. Nothing material about runtime behavior is left unstated.

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?

Five tight sentences, front-loaded with what the tool does, then environment, limits, atomicity, availability, and return value in descending order of importance. Every clause carries operational information; there is no filler or restatement of the name.

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

Completeness4/5

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

For a complex code-execution tool with no output schema and no annotations, the definition covers execution environment, quotas, atomicity, error signaling ('a 404 means it does not'), and the return value ('Returns the created ids'). The only substantive omission is the `room` parameter and its accepted pattern, which an agent would otherwise have to infer from the schema alone.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it explains three parameters in context: source (16 KB program body receiving emit/rand/param), seed (drives the seeded rand()), and params (2 KB, read via param(name)). The `room` parameter, which has a constrained pattern, is never mentioned, leaving one of four parameters undocumented in both places.

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 ('Run a small JavaScript program on the server') plus its defining scope ('emits many entities'), with concrete examples (a stair, a village, a forest). The 'many entities' framing plus 'validated like world_place' lets an agent distinguish this bulk-generation tool from the single-entity world_place sibling without opening either schema.

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 real prerequisite ('Works only where the server has generators switched on (a 404 means it does not)') and implicitly routes single placements to world_place via the 'many entities' and validation comparison. It never explicitly states when not to use it or names an alternative for a one-off placement, so it stops short of full when/when-not guidance.

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

All Haze City tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.