Sibyl

video_status

Poll a Veo video generation by operation name, then download the rendered MP4 to the specified output path.

Instructions

Poll a Veo generation by its operation name. When done, downloads the mp4 to output_path.

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": {
      "operation": "<operation>",
      "output_path": "<output_path>"
    },
    "name": "video_status"
  }
}

Input Schema

Name	Required	Description	Default
`operation`	Yes	The operation name from generate_video.
`output_path`	Yes	Where to save the .mp4 when ready.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the core behavior (poll and download) but does not disclose important traits like whether the tool blocks until the generation completes, what it returns (if anything), error handling, or behavior if the generation fails. This is insufficient for a polling tool.

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 a single sentence that is front-loaded and free of fluff. Every word contributes meaning, making it appropriately concise.

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

Completeness2/5

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

Given no annotations, no output schema, and only two parameters, the description is too sparse. It does not explain the polling behavior (e.g., blocking vs. non-blocking), return value, or failure modes. For a status tool, this incomplete context could leave an agent uncertain about how to use it effectively.

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 100%, with both parameters clearly described in the schema. The description adds little beyond the schema—just affirms that it downloads to output_path and uses the operation name. Baseline 3 is appropriate.

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?

The description clearly states the tool's function: 'Poll a Veo generation by its operation name. When done, downloads the mp4 to output_path.' It uses a specific verb (poll) and resource (Veo generation), and the download action distinguishes it from sibling tools like generate_video or generate_image.

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?

The description implies usage after generating a video (polling a generation), but does not explicitly say 'use after generate_video' or mention alternatives. The schema adds context by noting 'operation' comes from generate_video, but the description itself lacks explicit when-to-use guidance.

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

Deploy Server