Skip to main content
Glama

fill_idle_production

Assigns the first available basic building to every idle city in one call, preventing lost production and flagging cities with nothing buildable.

Instructions

Give every idle city something to build, in one call.

Walks all your cities, finds the ones producing nothing, and starts the first
basic building each one can actually make (monument → granary → water mill →
sewer → builder as a fallback).

Why this exists: idle production is not banked, it evaporates that turn. At 20
cities that is an annoyance; at 90+ the end_turn gate names a dozen idle cities
per turn and the per-city set_city_production tool would need a dozen round
trips to clear it. The choice itself carries no strategic content — cities that
need a real decision (spaceport city, front-line production) are never idle in
the first place, so this never touches them.

Returns a per-city list of what was started, plus any city with nothing
buildable at all (those need manual handling).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fill_idle_production"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full disclosure burden and does so well: it explains the city-walking behavior, the exact fallback order of buildings, that idle production is not banked, and that the return includes cities with nothing buildable. It clearly implies a game-state mutation 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.

Conciseness4/5

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

The description is front-loaded with the core action and remains well structured. It is somewhat longer than strictly necessary, but the rationale and return-value details are useful rather than wasteful.

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?

Given a zero-parameter mutation tool with no annotations and an existing output schema, the description provides everything an agent needs: purpose, usage context, alternative tool, fallback selection order, and the shape of the response including unbuildable cities.

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 has zero parameters, so there is no parameter semantics to explain; the baseline for zero-param tools is 4. The description appropriately focuses on behavior rather than inventing parameter details.

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 states a specific verb and resource: it walks all cities, identifies idle ones, and starts the first buildable basic building. It explicitly contrasts this with the per-city set_city_production tool, so an agent can distinguish the two without inspecting schemas.

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

Usage Guidelines5/5

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

It says exactly when to use this tool (idle cities whose production is evaporating) and when not to worry about it (cities that need strategic decisions are never idle). It also names the alternative, set_city_production, and explains why this bulk tool exists.

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