Skip to main content
Glama
Sign In
civ6-mcp

civ6-mcp

by j4ckl1u
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_unit_promotions

Read-only

Lists available promotions for a specified unit, filtered by promotion class and XP eligibility, so you can choose a valid upgrade.

Instructions

List available promotions for a unit.

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

Shows promotions filtered by the unit's promotion class.
Only units with enough XP will have promotions available.

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": {
      "unit_id": "<unit_id>"
    },
    "name": "get_unit_promotions"
  }
}

Input Schema

NameRequiredDescriptionDefault
unit_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.11

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true. The description adds behavioral info about filtering by promotion class and XP requirement, going beyond annotations without contradiction.

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?

Two sentences plus an Args line, all essential information front-loaded (purpose in first sentence). No unnecessary words or repetition.

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?

Covers purpose, parameter origin, filtering conditions, and prerequisites (XP). With an output schema provided, return values are covered externally. The description is fully sufficient for an agent to use this tool correctly.

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?

The description explains the single parameter unit_id as 'The unit's composite ID (from get_units output)', adding essential context beyond the schema's type and title, especially with 0% schema description coverage.

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 'List available promotions for a unit' with a specific verb ('List') and resource ('available promotions for a unit'), distinguishing it from sibling tools like promote_unit which applies a promotion.

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 clear usage context: it lists promotions filtered by promotion class and only for units with enough XP. However, it does not explicitly contrast with sibling tools like promote_unit or when not to use.

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