Skip to main content
Glama
TheoTown MCP Server

TheoTown MCP Server

by d-init-d

theotown_get_job

Check the progress and execution status of a submitted construction job, so you can monitor whether planned building work is queued, running, completed, or failed.

Instructions

Query progress and execution status of a submitted construction job.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_id": "<job_id>"
    },
    "name": "theotown_get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault
errorNo
job_idYes
resultNo
statusYes
progressNo
created_atYes
session_idNo
updated_atYes
total_stepsNo
failed_stepsNo
attempted_stepsNo
completed_stepsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Query' implies a read-only, non-mutating operation, but the description says nothing about polling expectations, whether job status is retained after completion, error behavior for unknown/expired job IDs, or whether the call blocks.

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 with no filler or redundancy. It is efficient, though its brevity contributes to the gaps in the other dimensions rather than reflecting deliberate minimalism.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is not required, and the tool's scope is narrow. Still, for a job-polling tool with zero annotation coverage and an undocumented job_id, the definition leaves an agent without enough context on lifecycle, polling, or failure modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter job_id has no documented format or origin anywhere. The description implies it references a 'submitted construction job', which hints at where it comes from, but it adds no format, example, or lifecycle detail to compensate for the empty schema.

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 specific verb ('Query') and resource ('progress and execution status of a submitted construction job'), which is meaningfully distinct from siblings like theotown_cancel_job or theotown_get_status. It doesn't explicitly name how it differs from theotown_get_status, but the 'submitted construction job' scoping does most of the differentiation work.

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 implied by 'submitted construction job' — an agent can infer this is a follow-up poll after launching a build/plan job. However, there is no explicit when-to-use guidance, no mention of which sibling produces the job_id, and no statement about alternatives such as theotown_get_status.

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