Skip to main content
Glama
Sign In
TiledMCP

TiledMCP

by PengLx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Preview creating a map layer

tiled_create_layer
Read-only

Create an empty tile, object, image, or group layer in a Tiled map at a given index, pinning revisions for a safe, expiring change set without modifying project assets.

Instructions

Plans one empty tile, object, image or group layer at a root/group insertion index, pins map/dependency revisions, and returns an expiring change set without modifying project assets. Image layers require imagePath and may pin expectedImageRevision; other layer types reject both image fields.

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>",
      "name": "<name>",
      "expectedMapRevision": "<expectedMapRevision>",
      "expectedDependencyRevisions": "<expectedDependencyRevisions>",
      "type": "<type>"
    },
    "name": "tiled_create_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
typeYesLayer kind. imagelayer requires imagePath; all other kinds forbid imagePath and expectedImageRevision.
indexNo
mapPathYesCanonical project-relative POSIX path; absolute paths and .. are forbidden
imagePathNoProject-relative image path. Required only when type is imagelayer.
parentGroupIdNo
expectedMapRevisionYesSHA-256 revision returned by a read or preview
expectedImageRevisionNoOptional current image revision pin. Allowed only when type is imagelayer.
expectedDependencyRevisionsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description adds value by disclosing the expiring change set and the no-modification guarantee. No contradictions.

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 concise sentences, front-loaded with key information, no redundant words.

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 output schema exists and annotations cover safety, description adequately covers behavioral constraints and conditional parameters. Could mention that the change set is expiring, but that's already stated.

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

Parameters4/5

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

Schema coverage is 56%; description adds the crucial conditional logic for imagePath and expectedImageRevision based on type, which is not fully captured in the schema descriptions. Also hints at 'root/group insertion index' for parentGroupId.

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?

Description uses specific verb 'plans' and resource 'empty tile, object, image or group layer', clearly distinguishing from sibling tools like tiled_create_map (which creates actual maps) and tiled_preview_edits (general edits).

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?

Context is clear (preview a new layer), but no explicit when-not-to-use or alternatives are mentioned. However, the purpose and sibling list imply the proper context.

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