Skip to main content
Glama

Murnau VFX Price

lab_murnau_vfx_preis
Read-only

Price of a Murnau VFX node job (the paid AI nodes of the Murnau editor: outpaint, relight, crowd-fill, person-maske, freistellen, video-denoise, video-extend …) — free, nothing is booked. The same server function the editor's price check and the actual booking use. Without session_id/media_id the price is computed from dauer_s/breite/hoehe/fps; with them, from the real media of that session. Name the price to the person and only start lab_murnau_vfx_auftrag after their yes.

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": {
      "task": "<task>"
    },
    "name": "lab_murnau_vfx_preis"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNo
taskYesMurnau VFX task, e.g. relight, outpaint, person-maske, video-denoise
hoeheNo
breiteNo
paramsNoNode parameters that change the price (e.g. upscale_factor)
dauer_sNo
media_idNoMedia in that session's pool
session_idNoMurnau session (lab.thefilmradar.com/murnau/?session=…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

readOnlyHint=true is already declared, but the description adds real value on top: 'free, nothing is booked' rules out side effects, and 'the same server function the editor's price check and the actual booking use' guarantees the quote matches the eventual charge. It does not cover latency, auth, or error behavior, which keeps it from a 5.

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 purpose, then the no-cost reassurance, then the mode logic, then the workflow mandate. The parenthetical task list is long but useful; the middle sentence about being the same server function is slightly redundant with the 'free' clause.

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 an 8-param tool with a nested object and no output schema, the description covers purpose, cost model, input modes, and the follow-up workflow. It omits what the returned price actually looks like (currency, units, per-task breakdown), which matters given there is no output schema.

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?

At 50% schema coverage the description must carry weight, and it does: it defines a conditional split — dauer_s/breite/hoehe/fps without session_id/media_id, real media with them — that the schema cannot express. Only 'params' and 'task' nuances are left to the schema's own 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?

States a specific verb+resource (price of a Murnau VFX node job) and immediately disambiguates by enumerating the covered node types (outpaint, relight, crowd-fill, …). It is clearly distinguishable from sibling booking/status tools like lab_murnau_vfx_auftrag and lab_murnau_vfx_status.

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?

Explicit routing: call this first, name the price to the person, and only then start lab_murnau_vfx_auftrag after their yes. It also tells the agent which parameter combinations select which pricing mode, so when-to-use is fully prescribed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources