Skip to main content
Glama
archi-max

civ6-mcp

by archi-max
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

upgrade_unit

Upgrade a unit to its advanced form, like Slinger to Archer, when technology and gold allow. The upgrade consumes the unit's remaining movement, so plan carefully.

Instructions

Upgrade a unit to its next type (e.g. Slinger -> Archer).

Args:
    unit_id: The unit's composite ID (from get_units output)

Requires the right technology, enough gold, and the unit must have
moves remaining. The unit's movement is consumed by upgrading.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unit_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.11

TDQS

A4.4/5.0
Behavior4/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. It discloses that upgrading consumes movement and requires specific conditions, but lacks details on failure modes or additional effects beyond movement consumption.

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 succinct: one sentence for purpose, then clear bullet-point-like style for arguments and requirements. No unnecessary words, earning its place.

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?

Given the tool has one parameter, no annotations, and an output schema (not detailed but exists), the description covers key aspects (purpose, prerequisites, side effects). It omits return value details, but the output schema compensates.

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?

The only parameter, unit_id, is described as 'The unit's composite ID (from get_units output)', providing crucial context beyond the schema's type integer. This helps the agent understand where to obtain the value, though a format example would be helpful.

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?

The description clearly states the action ('Upgrade a unit to its next type') with an example ('Slinger -> Archer'), distinguishing it from sibling tools like promote_unit which have different functions.

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 specifies prerequisites (right technology, enough gold, moves remaining) and side effects (movement consumed), guiding the agent on when to use the tool. However, it does not explicitly mention when not to use or provide 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