Skip to main content
Glama
Sign In
TiledMCP

TiledMCP

by PengLx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Render a labeled tileset sheet

tiled_render_tileset_sheet
Read-onlyIdempotent

Renders a bounded page of a tileset with each tile labeled by its local ID. Handles atlas and image-collection tilesets, supporting configurable columns and page size.

Instructions

Renders one bounded page of a referenced tileset (atlas or image-collection), with every tile labeled by its local ID. Collection pages walk sparse local ids ascending, read each tile's own verified, revision-pinned image, and are limited to 64 tiles per page.

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": {
      "mapPath": "<mapPath>",
      "tilesetAssetId": "<tilesetAssetId>"
    },
    "name": "tiled_render_tileset_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based tileset sheet page index
scaleNo
columnsNoMaximum number of tile columns on a sheet page
mapPathYesCanonical project-relative POSIX path; absolute paths and .. are forbidden
pageSizeNo
tilesetAssetIdYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds valuable behavioral context: for collection pages, it walks sparse local IDs ascending, reads verified revision-pinned images, and is limited to 64 tiles per page. No contradiction.

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?

Two sentences with no fluff. Purpose is front-loaded in the first sentence, and the second adds precise behavioral details.

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?

Has output schema, so return values are defined. Description is fairly complete for a rendering tool, explaining collection page behavior. However, it omits details about atlas behavior.

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

Parameters2/5

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

Schema description coverage is 50%, but the description adds no parameter-level meaning. It mentions 'bounded page' and '64 tiles per page' which relate to page and pageSize, but does not explain individual parameters. The description should compensate for uncovered schema but does not.

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 renders a bounded page of a tileset with every tile labeled by local ID, distinguishing it from other render tools like tiled_render_tiles which likely render without labels.

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 rendering labeled sheet pages but does not explicitly state when to use this tool over alternatives, nor provides when-not-to-use guidance.

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