Skip to main content
Glama

Murnau VFX Job

lab_murnau_vfx_auftrag

Start a paid Murnau VFX node job in a Murnau session — the same route the editor's start button uses (session ownership, allowed tasks, price, booking). Requires bestaetigt_credits equal to the current price from lab_murnau_vfx_preis; if the price changed, nothing is created and the new price comes back (409). Inputs the editor normally prepares (input_url, params such as mask_url or prompt) must be given; the server refuses incomplete jobs before booking. Poll lab_murnau_vfx_status afterwards.

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": {
      "session_id": "<session_id>",
      "task": "<task>",
      "media_id": "<media_id>",
      "bestaetigt_credits": "<bestaetigt_credits>"
    },
    "name": "lab_murnau_vfx_auftrag"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNo
taskYesMurnau VFX task
hoeheNo
breiteNo
paramsNo
dauer_sNo
node_idNoVFX node id in the session graph, if the result belongs to a node
media_idYesInput media in that session's pool
input_urlNo
session_idYesMurnau session
bestaetigt_creditsYesThe price the person agreed to (from lab_murnau_vfx_preis)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description carries real weight: it discloses that the call is paid, that session ownership and allowed tasks are enforced, that a stale price yields a 409 with nothing created and the new price returned, and that incomplete jobs are rejected before booking. That is exactly the mutation-risk context an agent needs.

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-loads the action and the price precondition, then the failure mode, then the follow-up poll — a logical order with no filler. It is dense with parentheticals, but each clause carries real information.

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 paid, non-destructive mutation with no output schema and a nested params object, the description covers the preconditions, the refusal behavior, the 409 payload, and the follow-up status call. The remaining gap is the undocumented half of the input schema, which an agent would have to infer.

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 only 45% for 11 parameters, so the description partially compensates by explaining bestaetigt_credits (must match the price from lab_murnau_vfx_preis), input_url, and the params bag (mask_url, prompt). It leaves task, media_id, node_id, and the numeric geometry/duration fields entirely to the schema, so the compensation is incomplete.

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 and resource ('Start a paid Murnau VFX node job in a Murnau session') and immediately distinguishes itself from lab_murnau_vfx_preis and lab_murnau_vfx_status by naming them as the price source and the poll target. An agent can place this tool in a workflow without opening a schema.

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?

Gives an explicit call sequence: read lab_murnau_vfx_preis, pass bestaetigt_credits equal to that price, then poll lab_murnau_vfx_status. It also says inputs must be complete before calling because the server refuses incomplete jobs. It lacks an explicit 'do not use this if...' branch versus the plain lab_vfx siblings, but the routing is otherwise clear.

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