Skip to main content
Glama

get_render_job

Retrieve durable render job status—queued, running, completed, or failed—plus artifacts and scientific limits for inspecting musculoskeletal simulation evidence.

Instructions

Read durable queued/running/completed/failed render status, artifacts and scientific limits.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

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 full burden; it does add useful behavioral context by enumerating the job lifecycle states and the fact that results include artifacts and scientific limits. However, it says nothing about polling/refresh semantics, whether state transitions can be observed mid-flight, or any access constraints for a job that may belong to another user.

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 dense, front-loaded sentence with no filler; the verb and the returned payload are ordered ahead of the qualifying states. Slightly list-heavy but every clause carries information.

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 detail is legitimately omitted, and a one-parameter read tool is simple. Still missing is how an agent obtains a valid job_id and how this differs from the artifact-specific sibling, which matters given the stated overlap.

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

Parameters3/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 never explains where a job_id comes from (presumably a render/run submission sibling) or its format. The name is largely self-explanatory, so the gap is moderate rather than severe.

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 clear verb ('Read') and a specific resource set: render status across the lifecycle (queued/running/completed/failed), artifacts, and scientific limits for one job. The overlap with the sibling get_render_artifact (which this description also claims returns artifacts) is not addressed, so the boundary is slightly blurred.

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?

No explicit when-to-use, when-not-to-use, or alternative tool is named. An agent can infer this is a status-polling read for an existing job_id, but it must guess whether to call this or get_render_artifact for artifact retrieval, and nothing indicates whether the tool is safe to poll repeatedly.

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