Better Godot MCP

Overview Schema Source Related Servers Discussions Admin

tilemap

Create and manage Godot TileSets: add texture sources, set tiles, paint scenes, and list tilesets through direct actions for structured 2D level design.

Instructions

TileSet and TileMap management. Actions: create_tileset|add_source|set_tile|paint|list. Use help tool for full docs.

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": {
      "action": "<action>"
    },
    "name": "tilemap"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	Action to perform
`tile_size`	No	Tile size in pixels (default: 16, for create_tileset)
`scene_path`	No	Path to scene file (for list, paint)
`project_path`	No	Path to Godot project directory
`texture_path`	No	Texture source path (for add_source)
`tileset_path`	No	Path to TileSet .tres file (for create_tileset, add_source)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.20.0Jul 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedv1.5.1Mar 12, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations indicate non-read-only and nondestructive behavior, but the description adds no behavioral context beyond listing actions. No disclosure of side effects, permissions, or mutation scope. For a management tool, this is insufficient transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is very short, with one sentence and a list. While concise, it sacrifices completeness by deferring to the help tool. Front-loads purpose but lacks structured details.

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

Completeness2/5

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

With 6 parameters, a required action, and an output schema present, the description is inadequate. It relies on the help tool for full documentation and does not explain return values or action-specific behavior. Self-contained usage is not possible.

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%, so baseline is 3. The description maps actions to the action enum but does not explain parameter interplay or provide context beyond the schema descriptions. No added value over schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'TileSet and TileMap management' and lists five concrete actions, clearly indicating the tool's domain. However, it does not differentiate from sibling tools like 'scenes' or 'resources' that might overlap, missing a chance to clarify uniqueness.

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 is provided on when to use this tool versus alternatives. The only reference is 'Use help tool for full docs,' which defers responsibility rather than offering decision-making context. There is no mention of prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server