Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

tilemap_set_cell

Set specific tile cells in Godot TileMaps to programmatically build and modify game level layouts and terrain.

Instructions

Set single tile cell. (Compatibility tool)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tilemap_set_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It fails to disclose mutation semantics (overwrite vs merge), error handling (out of bounds), or idempotency. The 'Compatibility tool' label suggests behavioral quirks but does not explain them.

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

Conciseness4/5

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

Extremely terse (two fragments) with no wasted words. While efficient in structure, it suffers from under-specification rather than verbosity. The core action is front-loaded.

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?

Given the complexity of tilemap operations and the open schema, the description is inadequate. It omits critical domain concepts like coordinates, atlas positions, or tile sources needed to actually invoke the tool, providing only the barest operational hint.

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

Parameters1/5

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

With 0% schema description coverage and 'additionalProperties: true', the description must specify the expected cell parameters (coordinates, tile ID, layer). It mentions none of these, leaving the user to guess the required properties beyond the generic 'timeoutMs' and 'autoConnect'.

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?

States a specific action ('Set') and resource ('single tile cell'), distinguishing it from siblings like 'tilemap_fill_rect' (batch) and 'tilemap_get_cell' (read). However, it lacks detail on what constitutes a 'cell' in this context.

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?

Provides only the cryptic note '(Compatibility tool)' which hints at deprecation or legacy use but offers no actionable guidance on when to use this versus alternatives (e.g., batch tools) or what 'compatibility' refers to.

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