Skip to main content
Glama
PengLx
by PengLx

Preview stamping a prefab region

tiled_preview_prefab
Read-only

Stamp a source map region as a prefab into a target map, copying tiles and optional objects while verifying source revisions for safe reuse.

Instructions

Stamps one source-map region as a prefab: tiles from one source tile layer — carried as tileset+localId references, so a target map missing the tileset fails closed — and optionally objects anchored inside the region's pixel bounds from one source object layer, materialized at planning time into ordinary setTiles and createObject operations against the target map (the plan itself is the frozen prefab; nothing re-reads the source at apply, and an optional expectedSourceRevision asserts the source up front). Empty source cells are skipped unless copyEmpty stamps the rectangle verbatim as erasure; extraTileLayers stamps additional source-to-target tile-layer pairs over the same region in one plan, and flipHorizontal mirrors the tile stamp with official TileLayer::flip bit semantics (tile layers only — combining it with objects fails closed). Objects outside the supported draft profile — custom properties, template instances, unknown members — fail closed rather than being silently dropped, as do cross-map object stamps between maps with differing tile sizes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYes
targetYes
mapPathYesCanonical project-relative POSIX path; absolute paths and .. are forbidden
objectsNo
copyEmptyNo
sourceMapPathYesCanonical project-relative POSIX path; absolute paths and .. are forbidden
flipHorizontalNo
extraTileLayersNo
expectedMapRevisionYesSHA-256 revision returned by a read or preview
expectedSourceRevisionNoSHA-256 revision returned by a read or preview
expectedDependencyRevisionsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

The description describes mutating operations (stamping tiles, creating objects) but annotations set readOnlyHint=true, a direct contradiction. This is a serious inconsistency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph that front-loads the core action but is overly wordy and lacks structure (e.g., bullet points or separate sections).

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

Completeness2/5

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

Given the tool's complexity, missing output schema details, and the annotation contradiction, the description fails to provide a reliable understanding. It omits discussion of return values and the contradiction undermines trust.

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?

With 36% schema coverage, the description adds significant meaning beyond schema, explaining copyEmpty, flipHorizontal, extraTileLayers, and how parameters interact (e.g., failing closed for cross-map stamps with differing tile sizes).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool stamps a source-map region as a prefab, involving tiles and objects. This distinguishes it from siblings like tiled_preview_template and tiled_preview_edits, though not explicitly.

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 when to use (stamping a prefab region) but lacks explicit guidance on when not to use or alternatives. It does not distinguish from other preview tools directly.

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