Civ6 MCP CN

Overview Schema Source Related Servers Discussions Admin

set_research_queue

Plan a tech or civic research route in advance so empty research slots auto-advance at end_turn. Queue items only consume when the slot is idle, and manual research still takes priority.

Instructions

Plan a research route once — end_turn auto-advances it on completion.

Args:
    items: Comma-separated type names in order, e.g.
           "TECH_NUCLEAR_FISSION,TECH_LASERS,TECH_NUCLEAR_FUSION".
           Empty string shows the current queues without changing them.
           "clear" empties the queue for the given category.
    category: "tech" or "civic" (default: tech)

The queue is a fallback, not a lock: it is only consumed when the
current research/civic slot is EMPTY at end_turn time, so a manual
set_research always wins. A queue item the engine rejects pauses the
queue with a visible event. Persisted per game — survives restarts.

Input Schema

Name	Required	Description	Default
`items`	No
`category`	No		tech

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses fallback semantics, that rejected items pause the queue with a visible event, that state is persisted per game across restarts, and what 'clear' destroys. This is unusually complete behavioral context for a mutation tool.

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 first line front-loads the core concept and auto-advance behavior, then the Args block documents parameters efficiently. Every sentence adds an operational detail; nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists, return values need not be explained. For a two-parameter queue mutation with no annotations, the description covers purpose, parameter formats, precedence rules, failure behavior, and persistence, leaving no critical gap for correct invocation.

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 description coverage is 0%, so the description must compensate, and it does: items is documented as comma-separated type names with an example, plus special values '' and 'clear'; category is documented as "tech" or "civic" with a default of tech. This fully compensates for the bare 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?

States a specific verb and resource: planning a research route via a persisted queue that end_turn auto-advances. It explicitly distinguishes itself from manual set_research by noting that a manual set_research always wins, so an agent can tell the two apart without opening schemas.

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

Usage Guidelines5/5

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

Explains exactly when the queue is consumed (only when the research/civic slot is EMPTY at end_turn), names the competing tool set_research and asserts its precedence, and documents special item values ('' to inspect, 'clear' to empty).

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

Deploy Server