GenFlick

Inspect 3D guides

native.inspect_film_three_d

DestructiveIdempotent

See clips' current 3D guides: returns each clip's image guide and 3×3 keyframe grid as images you can look at, with the shapes in its range and their links. Requests missing guides and waits for them (no credits). Inspect before saying links or framing are right. Guides show staging, camera and timing, never the finished look.

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.inspect_film_three_d"
  }
}

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

B3.4/5.0

Behavior3/5

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

The description adds real behavior beyond the annotations: it discloses the side effect of requesting missing guides and waiting for them, that this costs no credits, and that the images depict staging/camera/timing rather than the finished look. However, it never reconciles with destructiveHint=true and readOnlyHint=false, so an agent gets no signal about what state could be altered or whether the guide request is reversible — a notable omission for a tool flagged destructive.

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?

Front-loaded with what is returned, then the side effect, then the usage rule, then the limitation — a sensible order with no filler. It is dense but every clause carries information, though the colon-plus-list construction is slightly hard to parse on first read.

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 values need not be spelled out, and the description still usefully characterizes them. For a six-parameter, nested-argument, open-world tool flagged destructive, though, the gaps around the required session parameters and the destructiveHint flag leave the agent under-informed relative to the tool's complexity.

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

Parameters2/5

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

Schema description coverage is only 50%, so the description needs to compensate and largely does not. It implies clip scoping ('each clip's') but never mentions the maxItems=3 cap on clip_ids, nor explains read_skills, expected_catalog_version, or request_key, all of which are required and non-obvious in a native-tool context.

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?

States a specific verb and resource ('See clips' current 3D guides') and enumerates the returned artifacts: each clip's image guide, a 3×3 keyframe grid, plus the shapes in range and their links. It is clearly distinct from write-oriented siblings like native.edit_film_three_d_clip or native.render_film_three_d_guides by being read/inspect-oriented, though it never names native.read_film_three_d or native.wait_for_film_three_d_guides as alternatives.

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?

'Inspect before saying links or framing are right' gives an explicit usage condition and sequencing rule, and '(no credits)' sets a cost expectation for the implicit generation request. What is missing is routing guidance: nothing says when to call this versus the sibling that only waits or the one that renders guides.

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?