Skip to main content
Glama
Sign In
prompt-to-scene

prompt-to-scene

by 316sandon12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_task_status

Check the status of a Blender or Unity editor action, preview, or build request, optionally waiting up to 30 seconds for completion.

Instructions

Query or wait up to 30 seconds for any editor action, preview or build task.

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": {
      "request_id": "<request_id>"
    },
    "name": "get_task_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose a blocking wait behavior capped at 30 seconds. However, it omits other relevant traits such as authentication needs, polling vs long-polling behavior, failure modes, and what statuses may be returned.

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

Conciseness5/5

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

A single sentence that is front-loaded with the core action and contains no unnecessary words. It is appropriately sized for the tool's scope.

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?

For a tool with no annotations, no output schema, and 0% schema description coverage, the description is too sparse. It omits the meaning of request_id, what status values or task types to expect, and how it relates to sibling task-status or cancellation tools.

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%, so the description must compensate. It gives some meaning to wait_seconds by saying 'wait up to 30 seconds,' but it never mentions the required request_id parameter or what it identifies, leaving a major gap.

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 or wait) and resource (task status), with broad scope covering editor actions, previews, and builds. It does not distinguish itself from the sibling get_asset_status, so it falls short of a 5.

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?

The description implies usage by saying it can query or wait for any task, but it never states when to use this tool instead of alternatives like get_asset_status or cancel_task. No explicit exclusions or prerequisites are provided.

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