Skip to main content
Glama

render_status

Read-onlyIdempotent

Check how a Dinoctor animated video render is progressing: stage, 0–1 progress, frames, elapsed seconds, output file path, or error; poll every 10–30 seconds while it runs.

Instructions

Read-only: how the render started by render is going: stage, progress (0 to 1), frames and seconds so far; when done, the file path; or the error. Call every 10 to 30 seconds while running. Returns running: false when no render has run.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description goes further by disclosing the polling cadence, the progress scale (0 to 1), the field set of the response, the terminal success value (file path), the failure value (error), and a no-render sentinel. That is exactly the kind of behavior an agent needs to avoid hammering the endpoint or misreading results.

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?

Everything is front-loaded in two dense, colon-and-semicolon-delimited clauses with no filler sentences. The compression is slightly heavy to parse on first read, but every clause carries distinct information (status fields, cadence, terminal states).

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

Completeness5/5

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

There is no output schema, so the description carries the full burden of describing returns, and it does so field-by-field including the done, error, and idle cases. Combined with the polling guidance and the existing annotations, nothing an agent needs in order to call this correctly is missing.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless schema applies. Nothing in the description misleads about inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('how the render started by render is going') and enumerates the returned fields: stage, progress 0-1, frames, seconds, final file path, or error. It explicitly ties itself to the sibling 'render' as the operation that creates the state being polled, so an agent can distinguish it from render/cancel_render.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete operational guidance: poll every 10 to 30 seconds while running, and the sentinel 'running: false' when no render has run. What is missing is an explicit when-not rule (e.g., what to do instead once done, or that starting a render is done via 'render'), so it falls short of the 5 tier.

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