Skip to main content
Glama

build_region

Build a complete first-draft map from a RegionSpec, save it to the given path, and make it the open map so edit tools and render_preview work next.

Instructions

Build a complete first-draft map from a RegionSpec (see region_spec_schema), save it to out_path and make it the open map, so the edit tools and render_preview work next. Order: land, mountains, rivers/lakes, ground, forests, settlements, roads, realms, labels. A settlement on water is moved to land within 60 px (see warnings).

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": {
      "spec": "<spec>",
      "out_path": "<out_path>"
    },
    "name": "build_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes
out_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real side effects: a file is written to out_path, the result becomes the open map, settlements on water are silently relocated up to 60 px and reported in warnings. It omits overwrite behavior for an existing out_path, whether the previously open map is discarded or undoable, and any failure modes — significant gaps for a tool that replaces the working map.

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?

Three sentences, front-loaded with the primary action and effect, then the ordering detail, then the one surprising edge case. Every sentence carries distinct information with no restatement of the name.

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?

For a complex, state-changing generator with no annotations and no output schema, the definition covers the essential contract: input source, output location, resulting app state, and the warnings channel. The remaining hole is overwrite/idempotency and out_path formatting, which an agent would need before calling it safely on an existing file.

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?

Top-level schema coverage is effectively 0% (spec is an opaque $ref, out_path has no description at all). The description compensates partly by pointing to region_spec_schema and by naming the internal build order (land, mountains, rivers/lakes, ground, forests, settlements, roads, realms, labels), which tells the agent what the spec contents mean. It says nothing about out_path's expected format (path, extension, overwrite), which is the one parameter with zero schema help.

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?

States a specific verb and resource: build a complete first-draft map from a RegionSpec, save it to out_path, and make it the open map. The two clauses 'first-draft' and 'so the edit tools and render_preview work next' separate it cleanly from the add_*/paint_* siblings that modify an existing map.

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

Usage Guidelines4/5

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

The description makes the workflow position explicit: run this first to produce a draft, then use the edit tools and render_preview. It does not say when NOT to use it (e.g. against an already-open hand-edited map, or whether it replaces the current map), so it stops short of full alternative routing.

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