Skip to main content
Glama
Sign In

GenFlick

by com.genflick
OverviewDiscussionsAdmin

Review production

native.inspect_production_output
DestructiveIdempotent

Inspect actual saved media from an accessible linked production, using an exact returned resource identity.

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_production_output"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_idYes
argumentsYes
read_skillsYesExact 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_keyYes
publication_proposal_idNoFor native Social scheduling, the exact server-approved publication proposal. This identifier cannot confer approval by itself.
expected_catalog_versionYesFor 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, idempotent=true and openWorld=true, so the safety bar is lower, but the description's "inspect" framing sits in tension with a destructive, non-read-only operation and never explains what is written or consumed. What it does add is meaningful: the resource identity must be "exact" and previously "returned", which warns the agent that IDs cannot be guessed or synthesized.

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 front-loaded sentence with no filler; the key constraint (exact returned resource identity) is placed where it will be read. It is lean to the point of omitting necessary detail, but as prose it is well-formed.

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

Completeness2/5

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

For a six-parameter tool with a nested arguments object, two undifferentiated enums, required skill proofs, and a catalog version requirement, one sentence is far too thin — even though an output schema exists to cover return values. An agent would have to reverse-engineer the meaning of mode and kind entirely from enum strings.

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 50%, and the description only gestures at project_id ("linked production") and resource_id ("exact returned resource identity"). The two enums that drive behavior — kind (film/canvas/series/social/...) and mode (metadata/image/frames/audio/video) — have no description in either the schema or the description, and work_id, request_key, question, and the start_seconds/duration_seconds windowing are unexplained.

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 verb ("inspect") and resource ("actual saved media") are concrete, and it adds useful scoping ("from an accessible linked production"). However, it never distinguishes itself from close siblings such as native.read_production_outputs, native.inspect_asset, native.inspect_source, or native.inspect_generation_job, so an agent cannot tell from the text which inspection entry point to pick.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. Only the oblique prerequisite "accessible linked production" hints at preconditions; nothing tells the agent why it would choose this over read_production_outputs or inspect_asset.

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

All GenFlick toolsInspect
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