Skip to main content
Glama

unreal_job_status

Retrieve the status of an asynchronous Unreal Engine job by job ID to track progress and determine when editor operations finish.

Instructions

Get status for an asynchronous Unreal 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": "unreal_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 disclosure burden, yet it only implies read-only via the word 'Get'. It says nothing about behavior for unknown or expired job_id values, whether the returned state is terminal, whether results expire, or how often polling is appropriate.

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?

One short sentence with no filler and the resource stated up front. Its brevity is appropriate in form, though it contributes to the under-specification noted elsewhere rather than being a strength in itself.

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

Completeness2/5

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

With no annotations and no output schema, the description must explain what a status response contains (states such as pending/complete/failed) and any polling guidance. It supplies none of that, leaving an agent able to call the tool but unable to interpret or sequence the call confidently.

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?

The single job_id parameter has 0% schema description coverage, and the description adds no meaning: it does not say where job_id comes from (presumably returned by an async-starting sibling) or what format it takes. This is exactly the gap the description should fill for a low-coverage schema.

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 verb 'Get status' and resource 'an asynchronous Unreal job' are stated, and 'asynchronous' distinguishes it from the sibling status tools (unreal_get_status, unreal_get_editor_status). However, beyond that adjective the sentence largely restates the name 'unreal_job_status' and never says what a 'job' is or what status information is returned.

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 guidance, no mention of polling an async job versus checking editor or general status, and no named alternative. An agent must infer entirely from the tool name that this is the follow-up call after an async operation.

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