Skip to main content
Glama
Sign In
TiledMCP

TiledMCP

by PengLx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Render a staggered/hexagonal preview

tiled_render_hexagonal
Read-onlyIdempotent

Render a bounded region of a hexagonal or staggered TMJ map with Tiled's exact HexagonalRenderer, supporting atlas tilesets and skipping object layers.

Instructions

Renders a bounded region of one finite staggered or hexagonal TMJ map using the exact Tiled 1.12.2 HexagonalRenderer transform — staggered maps are the hexSideLength=0 degenerate case, matching the official class hierarchy — with cells compositing in the editor's row order on both stagger axes. Same strict profile as tiled_render_isometric: external atlas tilesets whose tile size matches the grid; image-collection tilesets, transparent-color keying, hexagonal rotation flags, and image or group layers fail closed, and object layers are skipped with their ids disclosed. Read-only.

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>",
      "region": "<region>"
    },
    "name": "tiled_render_hexagonal"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNo
regionYes
mapPathYesCanonical project-relative POSIX path; absolute paths and .. are forbidden
layerIdsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds significant behavioral details beyond these: compositing order, failure modes for image-collection tilesets and transparent-color keying, and the strict profile comparison. There is 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?

The description is a single sentence but conveys a lot of information efficiently. It is front-loaded with the main action. However, the dense clause structure could be slightly improved for readability, but it remains concise.

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

Completeness3/5

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

The tool is complex (hexagonal rendering with specific constraints), and an output schema exists but is not shown. The description explains behavioral constraints and failure modes well but does not describe the return value (e.g., image format). Given the complexity, a mention of the output type would improve completeness.

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 only 25% (only mapPath has a description). The description does not add meaning to the parameters (scale, region, layerIds) beyond implying region is the bounding area. For a tool with low coverage, the description should compensate but fails to explain parameter roles or 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 'Renders a bounded region of one finite staggered or hexagonal TMJ map using the exact Tiled 1.12.2 HexagonalRenderer transform', providing a specific verb and resource. It also distinguishes from the sibling tool tiled_render_isometric by noting the same profile and specific hexagonal/staggered map types.

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?

The description implies when to use (hexagonal/staggered maps) and mentions constraints (external atlas tilesets must match grid, image-collection tilesets fail closed). However, it does not explicitly state when not to use or provide direct alternatives beyond referencing tiled_render_isometric. The clarity about failure cases provides good 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