Skip to main content
Glama
Sign In

Framevine

by com.framevine
OverviewDiscussionsAdmin

Get generation status

get_generation_status
Read-onlyIdempotent

Check the status of one generation (node). Returns its status, progress percent (progressEstimated is true when it is estimated from typical run times rather than reported by the provider) and, when it failed, the failure reason; once complete, the output file id, media URL, thumbnail URL and dimensions. Poll this after starting a generation until the status is complete or failed. Once complete it also returns a small preview image (for a video, its poster frame) so you can see the result.

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": {
      "threadId": "<threadId>",
      "nodeId": "<nodeId>"
    },
    "name": "get_generation_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesNode id of the generation.
threadIdYesThread id the generation belongs to.
includePreviewNoAttach a preview image once complete (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare the safe read-only/idempotent profile, and the description adds substantial behavioral detail: progressEstimated semantics, failure reason, completed output fields, polling guidance, and the preview image behavior. It does not contradict the 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 purpose is front-loaded, followed by polling guidance and return behavior. The parenthetical explanation of progressEstimated earns its place by clarifying a potentially ambiguous field.

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

Completeness5/5

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

There is no output schema, so the description carries the burden of explaining returns, and it does so thoroughly: status, progress, failure reason, file/media/thumbnail details, dimensions, and preview image. For a three-parameter read-only polling tool, this is complete enough to invoke correctly.

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 all three parameters documented, including includePreview. The description does not add parameter-level syntax or constraints beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific verb and resource: checking the status of one generation (node). It clearly scopes the tool to a single generation, but it does not explicitly distinguish it from the closely related get_render_status sibling.

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 explicitly says to poll this after starting a generation until the status is complete or failed, which gives clear usage context. It does not state when not to use it or name alternative status tools such as get_render_status.

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

All Framevine toolsInspect
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