Skip to main content
Glama
Sign In

GenFlick

by com.genflick
OverviewDiscussionsAdmin

Export Film

export_film
DestructiveIdempotent

Export the approved saved edit directly as a movie through durable native work. Uses its frozen edit/motion specification and server-recorded approval; may consume existing credits within the ceiling.

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": {
      "proposal_id": "<proposal_id>",
      "request_key": "<request_key>"
    },
    "name": "export_film"
  }
}

Input Schema

NameRequiredDescriptionDefault
proposal_idYesOpaque authorized product identifier; never proof of access.
request_keyYesStable caller request key; reuse unchanged after a lost response.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true, and the description usefully adds what annotations cannot: the export consumes the server-recorded approval and its frozen specification, and may spend existing credits within a ceiling. It stops short of saying what a repeat export does to prior outputs or whether the work is asynchronous, which matters for a destructive, credit-consuming operation.

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

Conciseness5/5

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

Two tight sentences, front-loaded with the action and target, followed by the operative constraints (frozen spec, approval, credits). No filler or redundant restatement of the title.

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?

Output schema exists, so return values need no explanation, and the description covers approval, spec freezing, and credit spend for a destructive export. Missing only the operational follow-through (async/polling expectations, retry behavior on lost responses) that the request_key hint implies but never explains.

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 both parameters are already documented; the description only indirectly gestures at proposal_id via 'frozen edit/motion specification' and says nothing about request_key reuse. Baseline 3 applies since the schema carries the semantics.

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+object ('Export the approved saved edit ... as a movie') and adds scope qualifiers ('approved saved edit', 'frozen edit/motion specification') that separate it from editing tools like assemble_film_edit. It never names a sibling alternative explicitly, so differentiation still depends on the agent's knowledge of the wider toolset.

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

Usage Guidelines3/5

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

'Approved saved edit' implies the precondition (edit exists and is approved) but is never spelled out as a when-to-use rule, and there is no statement of when NOT to use it or what to do instead (e.g., assemble or revise first). Usage is inferable rather than guided.

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