Skip to main content
Glama
Sign In
game-art-mcp

game-art-mcp

by Cuvara
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

art.tilemap.create_spec

Create a structured map specification to define tilemap size, biome, layers, objects, and terrain rules for procedural generation.

Instructions

Create a MapSpecification for tilemap generation. Defines map size, biome, layers, objects, terrain rules.

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": {
      "map_id": "<map_id>",
      "width": "<width>",
      "height": "<height>",
      "biome": "<biome>",
      "tileset_id": "<tileset_id>",
      "layers": "<layers>"
    },
    "name": "art.tilemap.create_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoRandom seed for procedural generation
biomeYesBiome (e.g. "forest", "dungeon", "village")
widthYesMap width in tiles
heightYesMap height in tiles
layersYesMap layers
map_idYesMap identifier
objectsNoMap objects
tile_sizeNoTile size (default: 16)
tileset_idYesTileset to use
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

C2.9/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 of behavioral disclosure. It says 'Create a MapSpecification' but does not explain whether this mutates persistent state, requires a registered tileset, validates inputs, or returns a handle to the spec. The mention of 'terrain rules' lacks any corresponding schema field, which adds a minor inconsistency.

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 description is a single, focused sentence that front-loads the core action and resource. It names the containing feature ('tilemap generation') and a compact list of the things the object defines. No wasted words or filler.

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?

For a complex 10-parameter, 6-required tool with no annotations and no output schema, the description is too thin. It does not explain return values, side effects, prerequisites, or the relationship to related tools like register_tileset or build_ops. An agent would need to infer too much about how the MapSpecification is used downstream.

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 high (90%), and the schema already describes most parameters. The description only groups parameters into categories like 'map size, biome, layers, objects' and does not add semantics beyond that. It also references 'terrain rules', which do not appear in any parameter, so it adds limited value to what the schema provides.

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 clearly states the verb 'Create' and the resource 'MapSpecification', and the list of contents (map size, biome, layers, objects, terrain rules) gives a useful overview. It distinguishes this spec-creation tool from sibling operations like list_tilesets, validate, build_ops, and resolve_tiles by establishing that this is the initial specification step.

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?

The description gives no explicit instruction about when to use this tool versus alternatives such as art.tilemap.validate, art.tilemap.build_ops, or art.tilemap.register_tileset. 'For tilemap generation' is only a vague context cue, not a usage guideline. No prerequisites, sequencing, or exclusion conditions are mentioned.

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