Skip to main content
Glama
PengLx
by PengLx

Preview seeded procedural generation

tiled_preview_generate
Read-only

Generate deterministic tilemaps with value noise, cellular caves, or connected dungeons over a bounded region, then map values to tiles and return a mapEdit change set for preview.

Instructions

Computes a deterministic seeded value field over one bounded region — smooth value noise (stateless coordinate hash, so the same seed always reproduces the same output and results are translation-stable), a cellular cave automaton yielding exactly 0 (open) and 1 (wall), or a rooms-and-corridors dungeon yielding exactly 0 (floor) and 1 (wall) with every floor cell connected (sequential seeded stream drawn region-relative, so a shifted region reproduces the same layout) — then maps values to tiles through explicit [min, max) intervals (max 1 inclusive; unmatched cells are skipped for sparse generation) and returns an ordinary mapEdit change set carrying the setTiles writes. Math.random is never involved; a mapping that matches no cells fails closed, as does a dungeon region too small for one minimum room plus its wall ring.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedYes
regionYes
layerIdYes
mapPathYesCanonical project-relative POSIX path; absolute paths and .. are forbidden
mappingYes
generatorYes
expectedMapRevisionYesSHA-256 revision returned by a read or preview
expectedDependencyRevisionsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description discloses key behaviors: deterministic seeding, translation stability, failed-closed for unmatched cells or small dungeon regions, and math.random avoidance. Annotations declare readOnlyHint=true, which is consistent since the tool previews changes without applying them. No contradiction present.

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 moderately long but informative, front-loading the purpose. Every sentence adds value, though some technical details could be more succinct. It avoids redundancy with the schema and annotations.

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?

Given the tool's complexity (three generator algorithms, mapping intervals, edge cases), the description covers deterministic behavior, translation stability, failure modes, and the nature of the output (change set). The presence of an output schema further reduces burden.

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 low (25%), but the description compensates by explaining semantics of seed, region, generator types, mapping intervals, and failure modes. For example, the mapping section clarifies interval behavior and the generator section describes each algorithm's parameters and constraints.

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 that the tool computes deterministic seeded value fields (noise, cellular, dungeon) over a bounded region, maps values to tiles via intervals, and returns a mapEdit change set. This distinguishes it from sibling tools like tiled_preview_edits or tiled_preview_shape, which handle manual edits or shapes.

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 usage for procedural generation previews (noise, cellular, dungeon) but does not explicitly state when to use this tool versus alternatives like tiled_preview_edits or tiled_preview_scatter. No exclusion criteria or when-not-to-use guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PengLx/TiledMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server