Skip to main content
Glama
ty-meador

civ-v-llm-harness

by ty-meador

assign

Give units or cities a structured task in your Civilization V notebook, defining role, target, completion checks, and review triggers for later sessions.

Instructions

Give units or cities a structured assignment in my notebook: what they are for, where, when it is done and when to look again. A prose note (remember) says why; an assignment lets a later me -- after a context reset, in a new session -- see at once what each unit is doing and whether that still holds. role: a short word (escort, settle, improve, defend, explore, diplomacy...). purpose: one sentence. unit_ids / city_ids: mine, now; each is fingerprinted (type and creation turn; name and founding turn), so if an id later names a different unit the assignment says the assigned one is gone instead of following it. target: {x, y} a plot (a city site, a tile to improve, a city to take or hold), {unit_id, owner} a foreign unit, or {player} a civ or city-state. done_when (checked on every read; default "manual"): {kind: "unit_at"|"city_at"|"improvement", x, y} (x, y default to the target plot; unit_at takes unit_id, improvement takes improvement e.g. "FARM"), {kind: "building", city_id, building}, {kind: "tech", tech}. review (optional): {turn: N, hostile_within: plots, hp_below: percent} -- look again at turn N, when a visible hostile comes that close to an assigned unit or city, when an assigned unit's hp drops below. replace_id: this replaces that assignment, which is closed as replaced (the two never compete). The answer is the stored assignment reconciled right away (see assignments). One game read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleYes
reviewNo
targetNo
purposeYes
city_idsNo
unit_idsNo
done_whenNo
replace_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description fully carries the behavioral burden: fingerprinting behavior, done_when checked on every read with default manual, review triggers (turn, hostile proximity, hp), replace_id closes old assignment, and return is the stored assignment reconciled immediately in one game read.

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?

Front-loaded with purpose and contrast to remember, then systematically covers parameters. Despite its length, every clause adds necessary semantics for an 8-parameter nested tool; no redundant 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?

No output schema exists, but the description states the return ('stored assignment reconciled right away ... One game read') and covers all inputs. Combined with detailed behavioral notes, it is complete for a complex create/replace assignment tool.

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%, but the description defines every parameter: role, purpose, unit_ids/city_ids with fingerprinting semantics, target variants, done_when forms and defaults, review triggers, and replace_id behavior. It adds syntax and meaning beyond the bare schema types.

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 (Give ... assignment) and resource (units or cities in my notebook), and explicitly contrasts with remember, so the agent can distinguish siblings. It also names the assignments sibling for the return.

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 contrasts with remember: prose note says why, assignment persists structured state for later sessions. However, it does not mention when to use amend_assignment or close_assignment instead, so not full when/when-not 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