Skip to main content
Glama
lmwilki

civ6-mcp

by lmwilki
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

set_city_production

Set a city's production to build units, buildings, districts, or projects. Specify city ID and item details; optionally provide coordinates for district placement.

Instructions

Set what a city should produce.

Args:
    city_id: City ID (from get_cities output)
    item_type: UNIT, BUILDING, DISTRICT, or PROJECT
    item_name: e.g. UNIT_WARRIOR, BUILDING_MONUMENT, DISTRICT_CAMPUS, PROJECT_LAUNCH_EARTH_SATELLITE
    target_x: X coordinate for district/wonder placement (required for districts — use get_district_advisor to find best tile)
    target_y: Y coordinate for district/wonder placement

Tip: call get_cities first to see your cities and their IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
city_idYes
item_typeYes
item_nameYes
target_xNo
target_yNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior3/5

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

No annotations, so description carries full burden. Discloses that target_x/y required for districts and suggests get_district_advisor. Missing details on side effects, error behavior if coordinates are wrong, or whether it can set wonders. Adequate but not comprehensive.

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?

Concise: one-line purpose, bulleted args, helpful tip. Every sentence adds value. Well-structured and front-loaded.

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?

Covers core usage and typical workflow (get_cities, get_district_advisor). Output schema exists, so return format is documented. Missing details like case sensitivity of item_type or behavior if coordinates omitted for districts. Nearly complete.

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

Parameters5/5

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

Schema coverage 0%, so description adds essential meaning. Explains city_id source, gives enumerations for item_type and item_name, and clarifies target_x/y usage. Greatly enhances schema.

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?

Starts with 'Set what a city should produce' clearly stating verb and resource. Args list and sibling differentiation (get_city_production, set_city_focus) confirm distinct purpose.

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?

Provides tip to call get_cities first and notes when target_x/y are required (districts). However, no explicit guidance on when not to use this tool versus alternatives like set_city_focus.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lmwilki/civ6-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server