Skip to main content
Glama

A generation's status and files

generation
Read-onlyIdempotent

One generation by id: its status, progress, files and charge, waiting up to wait_seconds for it to finish first. Use it after generate answers with a video still running. Needs the key the generation was made with. Live from GET /v1/generations/{id}.

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": {
      "id": "<id>"
    },
    "name": "generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe generation id generate answered with (gen_ then 24 hex characters).
previewNoDefault true: a finished image comes back inline as image content besides its link.
wait_secondsNoSeconds to wait for the files before answering with the generation as it stands, 0 to 120. Images usually finish inside the default 60; a video takes minutes, so follow up with generation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: it may block up to wait_seconds, it requires the key the generation was made with, and it maps to GET /v1/generations/{id} — useful auth and timing context not in 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with what is returned before the usage note and prerequisites. The trailing endpoint reference is minor filler but does establish data provenance, so it largely earns its place.

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?

No output schema exists, yet the description enumerates the returned fields (status, progress, files, charge) and covers auth and long-running video polling. Adequate for a three-parameter read tool; only the absence of explicit guidance on what a not-yet-finished response looks like keeps it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns a bump by explaining the blocking semantics of wait_seconds ('waiting up to wait_seconds for it to finish first'), which is the one parameter whose effect is easy to misread. It says nothing about preview, but the schema already documents that fully.

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: fetch 'One generation by id' with its status, progress, files and charge. The singular framing implicitly contrasts with the plural sibling 'generations', so an agent can tell fetch-one from list-many without opening a schema.

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?

'Use it after generate answers with a video still running' gives an explicit trigger condition and even the follow-up pattern (keep calling while a video renders). It does not state when not to use it or name an alternative for listing/browsing, which keeps it short of a 5.

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.