GenFlick

Park your turn until the tasks you name need you: one finishes, stops or asks a question, or a message reaches you

native.wait_for_work

DestructiveIdempotent

Park your turn until the tasks you name need you: one finishes, stops or asks a question, or a message reaches you. No model calls are spent while you wait. until=any returns when any task is ready, all when every task is, question only when one asks something.

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

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

B3.4/5.0

Behavior3/5

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

The description adds genuinely useful behavior beyond the annotations: the exact conditions that end the wait (finish, stop, question, message) and that no model calls are spent while parked. It does not address timeout behavior, maximum wait duration, or what happens to already-terminal tasks -- important for a blocking call. The annotations' destructiveHint=true is not explained or contradicted, leaving the safety profile ambiguous.

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?

Three dense sentences, front-loaded with the wait condition before the cost note and the mode semantics. The first sentence restates the title almost verbatim, which is mild redundancy, but no sentence is filler and the 'No model calls are spent' rationale earns its place.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, but for a blocking call with six parameters (three undocumented) the description omits timeout/abort behavior and the relationship to the delegation flow that produces delegation_ids. Adequate for the core mechanic, thin for the operational edges an agent needs before parking its turn.

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 50%, so the description must carry real weight. It does define the semantics of until (any returns on the first ready task, all requires every task, question only on a question), which the schema lists as bare enum values with no explanations. However, work_id, request_key, read_skills, and publication_proposal_id remain undocumented in both places.

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?

The description states a specific action and resource: it parks the caller's turn until named delegated tasks finish, stop, ask a question, or a message arrives. That is enough to tell it apart from mutation or read siblings, but it never names the more specific wait tools it resembles (native.wait_for_canvas_work, native.wait_for_film_generation), so an agent must infer which wait applies to its situation.

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?

Usage is implied rather than instructed: 'the tasks you name' suggests it is for work already delegated via native.delegate_work, and the until modes hint at when each variant is appropriate. There is no explicit when-not-to-use statement, no mention of alternatives among the many wait_* siblings, and no guidance on what to do if a task already completed before calling.

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?