Skip to main content
Glama

Read a render

render_job
Read-onlyIdempotent

Read a render, or wait until it changes state.

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": "<job>"
    },
    "name": "render_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesId from render.
wait_sNoMax 50s.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / wait_s / description
      Previous value: -"Seconds to wait, at most 50."New value: +"Max 50s."
  2. Changed2 schema fields changed
    • changedInput schema / properties / job / description
      Previous value: -"The id render returned."New value: +"Id from render."
    • changedInput schema / properties / wait_s / description
      Previous value: -"Wait this many seconds. At most 50."New value: +"Seconds to wait, at most 50."
  3. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The one thing the description adds beyond them is that the call can block until the render changes state, which is genuinely useful. It stops short of explaining what happens on timeout, whether waiting consumes quota, or what the returned state looks like.

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?

A single short sentence with no filler, and the dual read/wait behavior is front-loaded. It is efficient but arguably under-specified rather than trimmed of excess.

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 two simple parameters and no output schema, the definition should at least gesture at what is returned when the render is read or what constitutes a state change. It covers the blocking behavior but leaves the payload and timeout semantics unstated, which is a meaningful gap for the only inspection tool of its kind.

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 100%, so both parameters are already documented with types and constraints (job id, max 50s wait). The description only implies that wait_s enables the blocking behavior and adds no format or interaction detail beyond the schema, so baseline 3 applies.

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

Purpose3/5

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

The description gives a verb and resource ('Read a render') and hints at a blocking/polling mode, but 'render' is never clarified as a job status object, and the wording drifts from the tool name render_job. It does not distinguish itself from siblings such as render or check_video, leaving the agent to guess whether this starts, inspects, or waits on a render.

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?

It implicitly presents two modes (immediate read vs. wait for a state change) but never states when to pick each one, nor any alternative tool such as check_video. There is no when-to-use or when-not-to-use guidance at all.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources