Skip to main content
Glama

Wait for generation

wait_for_generation
Read-only

Block up to seconds (max 25) until the generation finishes, then return it. Call repeatedly for long video renders.

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": {
      "generation_id": "<generation_id>"
    },
    "name": "wait_for_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
secondsNo
generation_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, the description explains that the call blocks for up to `seconds` with a maximum of 25 and may need to be repeated for long renders. It does not describe timeout behavior or error conditions, but it adds meaningful operational context beyond the read-only annotations.

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?

The description is two short sentences with no wasted wording. The blocking behavior is front-loaded and the repeated-call guidance follows naturally.

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?

The output schema exists, so return-value documentation is unnecessary. The description covers the key blocking and polling semantics, though it could clarify timeout or error behavior for an agent waiting on long renders.

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 0%, so the description needs to carry parameter meaning. It explains `seconds` as a blocking duration with a max of 25, but it does not add any meaning for `generation_id` beyond the parameter name.

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 verb and resource: wait for a generation until it finishes, then return it. It clearly distinguishes blocking behavior from simple retrieval, though it does not explicitly name a sibling such as get_generation.

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?

It gives clear usage guidance by saying to call repeatedly for long video renders, which implies the intended polling pattern. It does not explicitly state when to prefer get_generation instead, but the blocking behavior provides strong context.

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