Skip to main content
Glama

Render still pictures

render_frames

PNG frames at times in seconds; poll the pending job.

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": {
      "source": "<source>",
      "at_s": "<at_s>"
    },
    "name": "render_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
at_sYesSeconds.
widthNoPixels.
sourceYesAs in render.
wait_sNoMax 50s.
idempotency_keyNoRetry key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / at_s / description
      Previous value: -"Seconds, at most 24."New value: +"Seconds."
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "Retry key.",
      +  "type": "string"
      +}
    • addedInput schema / properties / wait_s
      Added value: +{
      +  "description": "Max 50s.",
      +  "type": "number"
      +}
    • changedInput schema / properties / width / description
      Previous value: -"Width, pixels."New value: +"Pixels."
  2. Changed6 schema fields changed
    • changedInput schema / properties / at_s / description
      Previous value: -"Times, in seconds. At most 24."New value: +"Seconds, at most 24."
    • removedInput schema / properties / source / additionalProperties
      Removed value: -false
    • changedInput schema / properties / source / description
      Previous value: -"What to render."New value: +"As in render."
    • removedInput schema / properties / source / properties
      Removed value: -{
      -  "entry": {
      -    "type": "string"
      -  },
      -  "files": {
      -    "additionalProperties": {
      -      "type": "string"
      -    },
      -    "type": "object"
      -  },
      -  "kind": {
      -    "enum": [
      -      "hyperframes",
      -      "remotion",
      -      "blender",
      -      "mitsuba",
      -      "shader",
      -      "film",
      -      "ffmpeg",
      -      "composite"
      -    ],
      -    "type": "string"
      -  },
      -  "project_id": {
      -    "type": "string"
      -  },
      -  "url": {
      -    "type": "string"
      -  }
      -}
    • removedInput schema / properties / source / required
      Removed value: -[
      -  "kind"
      -]
    • changedInput schema / properties / width / description
      Previous value: -"Picture width in pixels."New value: +"Width, pixels."
  3. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false, so the agent knows this mutates external state and is not idempotent. The description adds two genuinely useful traits beyond that: the output is PNG stills and the operation is asynchronous and requires polling. It stops short of explaining job lifecycle, timeouts, or what happens if `at_s` exceeds the source duration.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short clauses with no wasted words, but the extreme terseness comes at the cost of grammar and clarity — neither clause is a complete sentence, and the polling instruction is buried after the output description rather than front-loaded as the operational step.

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?

For a 5-parameter tool with a nested `source` object and no output schema, the definition covers the essentials (PNG output, second-based timing, async polling) but omits how the job is identified, what polling returns, and failure modes. Adequate to attempt the call, thin for handling the result.

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 every parameter already carries a description ("Seconds.", "Pixels.", "Max 50s.", "Retry key."). The description adds only the units clarification for `at_s`, which the schema already states; it adds nothing about `source` beyond the schema's cross-reference to `render`, or about the 24-item cap.

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?

"PNG frames at times in seconds" identifies the resource produced (PNG stills at given timestamps) and implicitly contrasts with the video-oriented sibling `render`, but it is a noun phrase with no verb, so the agent must infer that this triggers a render. The parenthetical about polling suggests it starts an asynchronous render job but never states that outright.

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?

"poll the pending job" is the only procedural hint and it is compressed into a fragment with no subject or tool reference (poll with `render_job`? how often?). There is no statement of when to choose this over `render`, `render_job`, or `check_video`, and no prerequisites or limits are given.

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