Skip to main content
Glama
lmwilki

civ6-mcp

by lmwilki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

recruit_great_person

Recruit a Great Person by spending your Great Person points. The unit spawns in your capital. Use get_great_people to see if recruitment is possible.

Instructions

Recruit a Great Person using accumulated GP points.

Args:
    individual_id: The individual's ID (from get_great_people output, shown after ability)

Requires enough Great Person points for that class.
The GP spawns in your capital. Use get_great_people to check [CAN RECRUIT] status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
individual_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.11

TDQS

A4.1/5.0
Behavior3/5

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

No annotations; description states GP spawns in capital and requires enough points. Could mention error behavior or other side effects, but basic constraints are covered.

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?

Four lines, front-loaded, clear structure with Args section. No unnecessary words.

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?

Simple tool with one param and output schema available. Description covers prerequisites, location, and data source. Adequate but could mention result format briefly.

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?

Single integer parameter is fully explained: source from get_great_people output, shown after ability. Completely compensates for 0% schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Describes recruiting a Great Person with GP points, clear verb and resource. Does not explicitly differentiate from sibling tools like patronize_great_person or reject_great_person, but context implies it.

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?

Explicitly directs user to check get_great_people for [CAN RECRUIT] status before using. Lacks explicit when-not-to-use, but provides clear prerequisite guidance.

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