GenFlick

Link 3D shapes

native.cast_three_d_shapes

DestructiveIdempotent

Link 3D shapes to the Film's characters, sets and props they stand for, or clear a link (element null). Links are saved on the element and apply to every clip of that 3D scene in this Film. Copy asset_id and include_path from read_film_three_d, inspect_film_three_d or prepare_three_d_film_handoff, and element ids from the Film's elements. Decide each link from what you inspected and the elements' descriptions; ask the creator when two elements fit equally. A tint change renders the affected guides again (no credits).

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

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.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real blast-radius context: links are stored on the element and 'apply to every clip of that 3D scene in this Film', and a tint change 'renders the affected guides again (no credits)'. It also clarifies that null element clears a link, which is the destructive path an agent needs to understand; only rate/limit or failure behavior is left unstated.

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?

The text is front-loaded with the action and the clear-link case, then the identifier sourcing, then the decision rule and the render side-effect. It is dense but every sentence carries operational information; only the phrasing 'Decide each link from what you inspected' is slightly redundant with the preceding sourcing sentence.

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

Completeness4/5

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

For a destructive, batched (up to 80 links) linking tool with an output schema, the description covers purpose, identifier provenance, clearing semantics, and the re-render consequence. Missing only explicit mention of the expected_revision concurrency guard and the required session-proof parameters, which the schema documents instead.

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?

Schema coverage is 50%, and the description compensates for the domain-critical fields by explaining where asset_id, include_path and element ids come from and that element=null clears the link. The remaining envelope parameters (work_id, request_key, read_skills, expected_catalog_version) are not discussed, though several carry their own schema descriptions.

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?

The description opens with a specific verb and resource ('Link 3D shapes to the Film's characters, sets and props') and also names the inverse operation ('or clear a link (element null)'). An agent can distinguish this from siblings like read_film_three_d or inspect_film_three_d purely from the text, since those are cited only as sources of identifiers.

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?

It states the workflow context clearly: gather asset_id/include_path from read_film_three_d, inspect_film_three_d or prepare_three_d_film_handoff, and element ids from the Film's elements, plus a decision rule ('ask the creator when two elements fit equally'). It does not state an explicit when-not-to-use condition or a prerequisite gate (e.g. required prior inspection or revision check), which keeps it short of a 5.

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?