Skip to main content
Glama
Sign In
TiledMCP

TiledMCP

by PengLx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Render selected tiles

tiled_render_tiles
Read-onlyIdempotent

Render specified local tile IDs from an external tileset, labeling each tile with its local ID for identification.

Instructions

Renders an explicit bounded, input-ordered selection of local tile IDs from one referenced external tileset (atlas or image-collection). Every selected tile is labeled with its local ID; the selection is never sorted, reduced or paginated. Collection selections read each tile's own image verified and revision-pinned; missing sparse ids fail closed.

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>",
      "localIds": "<localIds>"
    },
    "name": "tiled_render_tiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNo
columnsNoMaximum tile columns per row; defaults to 8 when omitted
mapPathYesCanonical project-relative POSIX path; absolute paths and .. are forbidden
localIdsYes
tilesetAssetIdYes
expectedMapRevisionNoSHA-256 revision returned by a read or preview
expectedTilesetRevisionNoSHA-256 revision returned by a read or preview

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds context about labeling, no sorting, no pagination, revision-pinning, and fail-closed for missing IDs. No contradiction with annotations.

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?

Three sentences are efficient and front-loaded with the core action. No wasted words, but the third sentence adds minor detail that could be integrated. Slightly dense, but overall good use of space.

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?

Given the output schema exists (so return values need not be described), the description covers the main behavior, input constraints, and edge cases. It lacks details on performance or prerequisites, but is complete for a focused rendering tool.

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

Parameters3/5

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

Schema description coverage is 57%. The description adds some context for localIds (explicit bounded, input-ordered, missing IDs fail closed) but does not explain other parameters like scale, columns, mapPath, tilesetAssetId, or revisions beyond what the schema already provides. Baseline 3 is appropriate.

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 states a specific verb ('renders') and resource ('explicit bounded selection of local tile IDs from one referenced external tileset'). It distinguishes from siblings like tiled_render_tileset_sheet and tiled_find_tiles by emphasizing explicit ID selection and lack of sorting/pagination.

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?

Clearly indicates when to use: for rendering selected tiles by local IDs from a single tileset. Implicitly excludes other use cases (e.g., sorting, pagination) but doesn't explicitly name alternatives. Context signals with many sibling tools provide implicit 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