Skip to main content
Glama
Sign In
TiledMCP

TiledMCP

by PengLx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Validate a Tiled map

tiled_validate
Read-onlyIdempotent

Validate Tiled map structure and MVP profiles without altering files. Ensures map paths are canonical and valid for project integration.

Instructions

Performs structural and MVP-profile validation without modifying the map, tilesets, or images.

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": "tiled_validate"
  }
}

Input Schema

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

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 provide readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds concrete context: the validation checks structural integrity and MVP-profile compliance. It also explicitly confirms no modification, which is consistent 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The entire description is a single, well-constructed sentence that conveys the essential information with no wasted words.

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 low complexity (single parameter, output schema present, rich annotations), the description is complete enough. It covers the scope of validation without needing to explain return values, as an output schema exists.

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 100% for the single parameter 'mapPath', which already has a clear description. The tool description does not add further semantics about the parameter beyond what the schema provides.

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 tool validates a Tiled map (specifically structural and MVP-profile), using a specific verb and resource. It distinguishes from modification tools by explicitly noting it does not modify the map, tilesets, or images.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for read-only validation, but does not explicitly outline when to use it versus alternatives like tiled_preview_validation_fixes, nor does it mention when not to use it. Usage context is implied rather than fully specified.

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