TheoTown MCP Server

Overview Schema Source Related Servers Discussions Admin

theotown_get_status

Retrieve live TheoTown city telemetry to monitor economy, population, happiness, infrastructure, utility balance, service coverage, and problem locations for informed decisions.

Instructions

Read live TheoTown city telemetry, including economy, population, happiness breakdown, infrastructure, estimated utility balance, sampled service coverage, and problem coordinates.

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": "theotown_get_status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Default
`day`	No
`name`	No	Unknown
`year`	No
`money`	No
`month`	No
`speed`	No
`taxes`	No
`width`	No
`demand`	No
`height`	No
`income`	No
`people`	No
`reason`	No
`disaster`	No
`problems`	No
`protocol`	No
`connected`	No
`happiness`	No
`utilities`	No
`is_sandbox`	No
`population`	No
`session_id`	No
`last_update`	No
`infrastructure`	No
`service_coverage`	No
`diagnostics_error`	No
`population_by_level`	No
`happiness_by_category`	No
`diagnostics_updated_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does contribute real behavioral nuance by marking the utility balance as 'estimated' and service coverage as 'sampled', warning the agent these are approximations rather than exact values, and 'Read' implies no mutation. However, it never states that the tool is side-effect free, nor anything about cost, latency, or data freshness beyond 'live'.

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?

A single front-loaded sentence that puts the verb and resource first and then enumerates returned domains without filler. The field list is dense but each item adds selection value; only minor tightening (e.g. grouping the estimates) would improve it.

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?

With zero parameters and an output schema present, the description need not document return structure, and it already names the returned domains, which is more than enough for a read tool. The remaining gap is behavioral rather than structural: no note on freshness guarantees, cost, or confirmation that nothing is mutated, which matters because no annotations exist to cover that ground.

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 zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. Schema coverage is 100% and empty by definition; nothing in the description conflicts with it.

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?

States a concrete verb and resource ('Read live TheoTown city telemetry') and enumerates the domains returned (economy, population, happiness, infrastructure, utilities, coverage, problem coordinates), which is enough to separate it from the build_*/execute_plan siblings. It stops short of explicitly contrasting with theotown_get_job, but the scope is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: the word 'live' suggests calling this for current state before planning or diagnosing problems, and 'problem coordinates' hints at a diagnostics role. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. theotown_get_job for job progress), so the agent must infer routing.

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

Deploy Server