Skip to main content
Glama

render_status

Read-only

Check render progress for one job or all jobs and confirm whether a render is currently in progress.

Instructions

Progress of one job, or of every job, plus whether a render is in progress.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "render_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description contributes one behavioral detail beyond that — that it also reports whether a render is in progress — but says nothing about the shape of the progress data, completion states, or what happens for an unknown job id.

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 sentence with no filler, and the scope distinction is front-loaded. The phrasing 'Progress of one job, or of every job, plus whether a render is in progress' is slightly convoluted but not padded.

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?

This is a simple read tool with one optional parameter and no output schema, so the burden on the description is modest. Still, with no output schema the description could reasonably explain what a status/progress result contains, and the ambiguity against get_status and list_render_jobs is left unresolved.

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?

Schema description coverage is 0%, so the schema gives the single job_id parameter no meaning at all. The description partially compensates by framing the parameter as selecting one job versus every job, but it never states that job_id is optional, what its format is, or what an invalid id does.

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?

The description states a specific resource and scope: render progress for a single job or all jobs, plus whether a render is currently running. It is clear enough to distinguish this from a job-mutating tool, but it never names or contrasts with the plausible overlaps in the sibling list (get_status, list_render_jobs).

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 only implied: supplying a job id yields one job's progress, and omitting it appears to yield all jobs. There is no explicit statement of when to prefer this over get_status or list_render_jobs, and no note on whether job_id is optional for the 'all jobs' case.

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