Skip to main content
Glama
ty-meador

civ-v-llm-harness

by ty-meador
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

trade_routes

Inspect your caravans and cargo ships and foreign routes entering your cities: yields, remaining turns, free slots, path, escorts, and nearby threats.

Instructions

Trade Route Overview: outgoing is Your TR (my caravans/cargo ships), incoming is With You (other civs' routes into my cities). Each row: from/to city and player, turns_left, per-turn yields for the origin (gold/science) and destination (gold_them / food_them / production_them). The religion columns are from_religion/from_pressure (left arrow) and to_religion/to_pressure (right arrow), omitted when that cell is blank. details is the gold and science hover. overview().free_trade_route_slots (available - used - queued) says whether a new caravan can be trained. path is the route line the map draws, plot by plot from the origin (vis=false where fogged), as the plot hover names it on any revealed plot. unit is the caravan/cargo ship on that line (ours always; a foreign one only while in sight) with escorted / escorted_by: our combat units on its plot, which an enemy must defeat before it can plunder; unit.matched is recorded (this caravan was seen alone on this route before), line or line_ambiguous (routes share the plot and no earlier read told them apart: it may be the other row's caravan). enemies_near_path lists visible enemy combat units within one hex of the line with their distance to the caravan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does so well for a read tool: it defines outgoing vs incoming, per-row fields, that religion columns are omitted when blank, that path points are vis=false where fogged, the meaning of unit.matched states, and that foreign units appear only while in sight. It stops short of stating this is a side-effect-free read, but for a zero-parameter query tool the disclosed semantics are substantial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense block with no paragraph breaks or front-loaded summary beyond the title, reading more like a field glossary than a tool description. Every clause is informative about the data, so little is wasted, but the lack of structure makes it harder to scan quickly.

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?

There is no output schema, so the description must explain return values, and it does so thoroughly across rows, religion columns, path, unit, and enemies_near_path. It is complete about the data shape; only the usage/routing context is absent.

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 tool takes no parameters, so the baseline of 4 applies. The description appropriately spends its space on output semantics instead of inventing parameter detail.

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

Purpose3/5

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

The description is headed 'Trade Route Overview' and details the shape of returned data, so the resource (trade routes) is identifiable, but it never states a verb or a crisp purpose like 'list all trade routes'. It also does not distinguish itself from close siblings such as available_trade_routes, establish_trade_route, or plunder_trade_route, leaving the agent to infer which one to call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. With siblings like available_trade_routes and plunder_trade_route in the toolset, the absence of any routing hint is a real gap.

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