Skip to main content
Glama
Sign In
TiledMCP

TiledMCP

by PengLx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Analyze tile usage

tiled_analyze_usage
Read-onlyIdempotent

Analyze tile usage across a Tiled map: return tile frequency, layer density, transforms, used tilesets, and unused local IDs, including hidden layers and tile objects.

Instructions

Returns bounded whole-map tile frequency, layer density, transform, used-tileset, and unused-local-ID summaries. Hidden layers and tile objects are included.

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_analyze_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapPathYesCanonical project-relative POSIX path; absolute paths and .. are forbidden
topTileLimitNo
expectedMapRevisionNoSHA-256 revision returned by a read or preview
expectedDependencyRevisionsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that hidden layers and tile objects are included, which is useful context beyond annotations. No contradictions; behavioral traits align with read-only operation.

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 sentences, no superfluous words. Every sentence adds value: one lists the computed summaries, the other notes inclusion of hidden layers and tile objects. Perfectly front-loaded.

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 presence of an output schema and clear annotations, the description adequately covers the tool's behavior for a read-only analysis tool. However, it could briefly mention that results are bounded (e.g., top tile limit) to clarify scope.

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 50% (2 of 4 parameters have descriptions). The description does not add any parameter details, failing to compensate for the undocumented parameters (topTileLimit, expectedDependencyRevisions). The agent must rely on schema alone, which is insufficient.

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 returns bounded whole-map tile frequency, layer density, transform, used-tileset, and unused-local-ID summaries, using a specific verb (returns) and resource (tile usage summaries). It distinguishes from sibling tools like tiled_get_map_summary and tiled_find_tiles by focusing on usage analytics.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as tiled_get_map_summary or tiled_find_tiles. The description does not provide context hints or exclude scenarios, leaving the agent to infer appropriateness.

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