Skip to main content
Glama
Sign In
TiledMCP

TiledMCP

by PengLx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List map objects

tiled_list_objects
Read-onlyIdempotent

Retrieve a bounded list of objects from a Tiled map, optionally filtered by a specific object layer, with configurable result limit.

Instructions

Returns a bounded list of objects from all object layers or one selected object layer.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
layerIdNo
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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, indicating safe operation. Description adds the bounded nature and layer filtering behavior, though no details on pagination or performance.

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?

Single sentence that is front-loaded, concise, and contains no superfluous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequately covers the main purpose and mode switching, but omits details like pagination, sorting, and output format (though output schema exists). Reasonable for a simple listing tool with strong annotations.

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 coverage is only 33% (mapPath described). Description does not explain limit or layerId parameters beyond implying layer selection. Does not compensate for missing schema descriptions.

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 it returns a bounded list of objects from all object layers or one selected layer. This distinguishes it from sibling tools like tiled_get_object (single object) and other listing tools.

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 vs alternatives such as tiled_get_object for a single object. The description does not mention exclusions or 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