Skip to main content
Glama
Sign In
civ6-mcp

civ6-mcp

by j4ckl1u
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_city_focus

Set a city's citizen yield priority to bias AI tile assignment toward food, production, gold, science, culture, or faith; use default to clear focus.

Instructions

Set a city's citizen yield priority.

Args:
    city_id: City ID
    focus: One of: food, production, gold, science, culture, faith, default
           'default' clears all focus settings.

Cities automatically assign citizens to tiles. This biases the AI
toward the chosen yield type when assigning new citizens.

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": {
      "city_id": "<city_id>",
      "focus": "<focus>"
    },
    "name": "set_city_focus"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusYes
city_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.11

TDQS

A3.9/5.0
Behavior3/5

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

Discloses it biases AI assignment, not direct control, but lacks prerequisites, side effects, or reversibility details.

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?

Concise with front-loaded purpose, though the 'Args' section is slightly redundant with the schema.

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?

Adequately covers key details for a simple tool; output schema exists but description doesn't reference return value.

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

Parameters4/5

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

With 0% schema coverage, description adds meaning by listing focus options and explaining 'default' clears settings.

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?

Clear verb+resource: 'Set a city's citizen yield priority.' Distinct from sibling tools like set_city_production.

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

Usage Guidelines3/5

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

Explains AI biasing and valid foci, but no explicit when-not-to-use or comparison to alternatives.

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