Skip to main content
Glama
Sign In
TiledMCP

TiledMCP

by PengLx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Preview tile-name registry edits

tiled_preview_tile_names
Read-only

Validate and preview tile name upsert/delete edits to the semantic registry, returning an expiring change set without modifying Tiled assets.

Instructions

Validates upsert/delete edits to the server-owned .tiledmcp/tile-names.json semantic registry and returns an expiring tileNameEdit change set — no Tiled asset is touched. Upserted names are restricted lowercase identifiers whose tilesets must exist as project .tsj files (re-verified at apply); deleting an unregistered name fails closed, the registry is bounded at 4,096 names, and the registry file's revision — or its absence — is pinned so a concurrent registry write fails closed. Apply replays the operations, verifies the result against the approved content hash, and rewrites the registry canonically.

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": {
      "operations": "<operations>"
    },
    "name": "tiled_preview_tile_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationsYes
expectedRegistryRevisionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A4.4/5.0
Behavior5/5

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

The description provides extensive behavioral details beyond the readOnlyHint annotation, including constraints on names (lowercase, 64 chars, tileset existence), registry bounds (4096 names), revision pinning, and the apply process. It fully discloses the tool's safety (no asset touched) and validation logic.

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 dense sentence that packs all necessary information. It is front-loaded with the core purpose and efficiently conveys constraints. However, it could be broken into shorter sentences or bullet points for easier parsing, though every clause adds value.

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 (array of discriminated objects, revision pinning), the description covers all behavioral aspects: what it validates, what it returns, constraints on names, tilesets, registry limits, concurrency handling, and the apply phase. It is thorough and leaves no major questions unanswered.

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?

With schema description coverage at 0%, the description should compensate for missing parameter docs. While it mentions the operations array (upserts/deletes) and name restrictions, it does not explain the other parameter (expectedRegistryRevision) or the detailed structure of each operation item beyond what is in the schema. Adds some value but not complete compensation.

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 validates upsert/delete edits to the tile-name registry and returns an expiring change set. It uses specific verbs ('validates', 'returns') and resources ('.tiledmcp/tile-names.json semantic registry'), which distinguishes it from sibling preview tools that operate on different assets.

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 the tool is for previewing registry edits before applying, and notes that no Tiled asset is touched (safe). However, it does not explicitly state when to use this tool versus alternatives like tiled_list_tile_names or tiled_apply_change_set, nor does it provide scenarios where it should not be used.

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