Skip to main content
Glama

assign_governor

Assign an appointed governor to a city. Requires governor already appointed; takes turns to establish.

Instructions

Assign an appointed governor to a city.

Args:
    governor_type: The governor type (from get_governors output)
    city_id: The city ID (from get_cities output)

Governor must already be appointed. Takes several turns to establish.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
governor_typeYes
city_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, but description discloses that assignment takes several turns and requires an appointed governor. No contradictions.

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?

Description is extremely concise, using three sentences with a list of arguments. Front-loaded with purpose.

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's simplicity and presence of output schema, description covers prerequisites and timing. Does not describe return value, but output schema handles that.

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?

Schema coverage is 0%, so description adds meaning by stating parameter origins: 'from get_governors output' and 'from get_cities output'. This helps agent locate valid values.

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?

Description clearly states action: 'Assign an appointed governor to a city.' It distinguishes from siblings like 'appoint_governor' and 'promote_governor'.

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?

Specifies prerequisites ('Governor must already be appointed') and side effect ('Takes several turns to establish'). Does not explicitly state when not to use, but enough context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lmwilki/civ6-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server