GenFlick

Wait for 3D guides

native.wait_for_film_three_d_guides

DestructiveIdempotent

Wait, for a bounded time, for these clips' guide renders when you need them yourself (generation already waits for them). Returns each guide as ready, failed with its reason, or still rendering when the wait ran long. Requests nothing: guides not started yet are reported so you can call render_film_three_d_guides.

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": {
      "work_id": "<work_id>",
      "arguments": "<arguments>",
      "expected_catalog_version": "<expected_catalog_version>",
      "read_skills": "<read_skills>",
      "request_key": "<request_key>"
    },
    "name": "native.wait_for_film_three_d_guides"
  }
}

Input Schema

Name	Required	Description
`work_id`	Yes
`arguments`	Yes
`read_skills`	Yes	Exact required native skills and their dependencies, copied from the accepted session bootstrap's skills array. Include only entries in that array. General mcp.* guides and native.{studio}.instructions are guidance, not native skill proofs.
`request_key`	Yes
`publication_proposal_id`	No	For native Social scheduling, the exact server-approved publication proposal. This identifier cannot confer approval by itself.
`expected_catalog_version`	Yes	For a new session, read a studios/{studio}/native/{pack} child toolset and copy invocation.catalog_version from a native tool descriptor. Do not use the top-level library version. For calls in an existing session, use that session proposal's catalog_version.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Beyond the annotations it discloses the three result states (ready, failed with reason, still rendering) and the important no-op guarantee that the call 'requests nothing'. However it leaves the destructiveHint=true annotation entirely unexplained and in apparent tension with 'Requests nothing', and says nothing about the read_skills/catalog-version proof requirements or request_key idempotency that the schema implies.

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?

Three sentences, no filler, with the core verb and exclusivity condition front-loaded. The opening clause ('Wait, for a bounded time, for these clips' guide renders') is comma-heavy and slightly hard to parse, and the bounded duration is never specified.

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-shape explanation is not required, and the description still covers the outcome states well. But for a 6-parameter tool with nested arguments and heavy session-bootstrap requirements, it omits how long 'bounded' actually is and whether the caller can influence it, leaving meaningful gaps.

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?

At 50% schema coverage the schema baseline is 3. The description only maps 'these clips' to the clip selection arguments; it adds nothing about work_id, read_skills, expected_catalog_version or request_key, which are the most opaque required parameters.

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 (wait) plus a specific resource (these clips' 3D guide renders) and scopes it to a bounded time. It also distinguishes itself from the sibling that creates the guides (render_film_three_d_guides), so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when ('when you need them yourself') and an explicit when-not ('generation already waits for them'), plus the follow-up path for unstarted guides ('guides not started yet are reported so you can call render_film_three_d_guides'). That is the full use/exclude/alternative triad.

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

All GenFlick tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?