Skip to main content
Glama

video_wait_for_prompt

Waits for a user's studio edit request, applies it via video_edit, answers with video_reply, then returns to waiting so collaboration continues.

Instructions

Wait for the user to type an edit request in the studio prompt box (ones the studio could not apply itself). Apply it with video_edit, answer with video_reply, then call this again to keep collaborating.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "video_wait_for_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutSecondsNodefault 600

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose that this is a blocking wait and implies a repeated polling loop, but it never says what happens on timeout, whether the call returns empty or errors, or in what form the user's request comes back. The 600s default lives only in the schema, so timeout behavior is left undefined.

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?

One compact sentence covering the trigger, the follow-up tools, and the loop, with the trigger front-loaded. Minor deduction for the awkward parenthetical and the mixed wait/apply framing that briefly blurs what the tool itself does.

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?

The description covers the collaborative loop and the routing to siblings, which is the core need. But with no annotations and no output schema, an agent still lacks the return shape and timeout/empty-result behavior for a blocking wait call, which is material for correct invocation.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already documents timeoutSeconds and its default. The description adds nothing about the timeout semantics, only that the tool should be called again after handling a request. Baseline 3 applies.

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 and resource: wait for an edit request typed into the studio prompt box, scoped to requests the studio could not apply itself. That qualifier distinguishes it from a generic wait, though the phrasing 'ones the studio could not apply itself' is slightly garbled and forces a re-read.

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 follow-on workflow: apply the request with video_edit, answer with video_reply, then call this again to keep collaborating. It does not name a when-not case or an alternative wait tool, but the trigger condition (unapplied user prompt) is stated clearly enough to route the agent.

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