Skip to main content
Glama
Sign In
TiledMCP

TiledMCP

by PengLx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Preview adding a tileset to a map

tiled_add_tileset_to_map
Read-only

Validates an external tileset, assigns its GID range to a Tiled map, and returns an expiring change set without modifying project assets. Supports pending tileset creation via change set ID.

Instructions

Validates one project-local external atlas TSJ, assigns its GID range after all current ranges, and returns an expiring map change set without modifying project assets. With createChangeSetId, a pending tileset-create change set's replayed prospective content stands in for a TSJ that does not exist yet; the attachment pins that prospective revision, so it applies after the create commits or atomically with it in one transaction.

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>",
      "tilesetPath": "<tilesetPath>",
      "expectedMapRevision": "<expectedMapRevision>",
      "expectedDependencyRevisions": "<expectedDependencyRevisions>"
    },
    "name": "tiled_add_tileset_to_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapPathYesCanonical project-relative POSIX path; absolute paths and .. are forbidden
tilesetPathYesCanonical project-relative POSIX path; absolute paths and .. are forbidden
createChangeSetIdNo
expectedMapRevisionYesSHA-256 revision returned by a read or preview
expectedTilesetRevisionNoSHA-256 revision returned by a read or preview
expectedDependencyRevisionsYes

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 aligns with annotations (readOnlyHint=true, destructiveHint=false) and adds detail: no project asset modification, expiring change set, and the interplay with createChangeSetId. This provides clear behavioral expectations beyond annotations.

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?

The description is three sentences front-loaded with the main purpose. Every sentence adds value, no fluff. Efficient and clear.

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 complex input (6 parameters, nested objects) and presence of an output schema, the description covers the core behavior and special case. It could mention the output schema nature but suffices for a preview 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 coverage is 67% (4 of 6 parameters described). The description adds context for createChangeSetId but no new details for other parameters. The schema does the heavy lifting, so 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 clearly states the action: validates a TSJ, assigns GID range, returns an expiring map change set. It specifies the resource (tileset to map) and distinguishes from sibling preview tools.

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 explains when to use the createChangeSetId parameter for pending tileset creation. However, it lacks explicit guidance on when to use this tool vs alternatives or when not to use it, though the context is implied.

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