Skip to main content
Glama

job_status

Retrieve a job's status, results, stdout and tracebacks, optionally waiting up to 30 seconds for completion. Use it to monitor asynchronous Blender tasks in a remote session.

Instructions

Read a job, including results, stdout and tracebacks. Optionally wait up to 30s.

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": {
      "session_id": "<session_id>",
      "job_id": "<job_id>"
    },
    "name": "job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
session_idYes
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it discloses the return contents (results, stdout, tracebacks) and that the call can block for up to 30 seconds, which goes beyond the schema. It says nothing about behavior for a nonexistent or incomplete job, error cases, or truncation of large stdout, leaving meaningful behavioral gaps for a read tool.

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?

Two short sentences, front-loaded with the action and return payload before the optional wait behavior. There is no filler or redundancy.

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?

With no annotations, no output schema, and 0% parameter coverage, the description should do more. It does cover the return payload and blocking semantics, but an agent still cannot tell how session_id and job_id relate, what a timeout returns, or how to interpret an unfinished job.

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 explain all three parameters. It only addresses wait_seconds ("wait up to 30s"), and even there adds no detail about the 0 default or the 30 maximum already in the schema, while job_id and session_id — including why both are required and how they relate — are entirely unexplained.

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?

"Read a job" is a specific verb+resource, and the description enumerates what the read yields (results, stdout, tracebacks), which separates it from cancel_job at a glance. It does not explicitly distinguish itself from session_status or get_logs, so the differentiation is only partial.

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?

"Optionally wait up to 30s" implies a polling/long-poll use case and tells the agent this call can block, which is useful context. However, there is no explicit when-to-use guidance, no mention of when to prefer a non-blocking check or get_logs, and no statement about what to do if the job is still running.

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