Skip to main content
Glama

Get generation

get_generation
Read-onlyIdempotent

Read a generation's status, outputs, or failure details. Completed results include all output files in provider order.

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": "get_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesGeneration ID returned by a generation tool.
waitNoWait for completion or failure. A timeout leaves generation running. Defaults to false, which returns the current status immediately.
timeoutNoHow long to wait for this generation when wait is true, in seconds. Defaults to and is capped at 45 seconds. Timing out leaves the generation running.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
inline_mediaNoSet to false to get only the JSON and resource links, without images or audio, for example when re-reading a result you have already seen. Defaults to true, which adds images and audio after their links while the result stays within its size limit.

Output Schema

NameRequiredDescriptionDefault
idYesGeneration ID. Pass it as id to get_generation.
typeYesRequested output type: image, video, audio, or svg.
modelYesModel ID the generation used.
statusYesCurrent generation status.
failureYesFailure details, or null when generation has not failed.
outputsYesOutput files in provider order. Empty until the generation completes.
created_atYesTime the generation was created.
brand_session_idYesBrand the generation belongs to.
message_for_assistantNoContext, explanations, or actionable guidance for the calling assistant. Hosts may display it, but it is not copy that must be shown to the user verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, and the description adds real value beyond them: completed results include all output files in provider order, and failures surface as 'failure details' rather than a bare error. What it omits (caller-visible auth scope, behavior for unknown IDs, cost) is minor.

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?

Two short sentences with zero filler; the core capability is front-loaded and the output-shape note follows logically.

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?

With an output schema present, the description need not explain return values, and the schema carries all parameter detail. It leaves only the poll-versus-wait decision and error-mode behavior unaddressed, which are small gaps for a read tool with full annotations.

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%, so every parameter including wait, timeout, llm_model, and inline_media is already documented. The description adds no parameter-level meaning beyond noting that results include all output files, which does not clarify any of the five inputs. 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?

The description opens with a specific verb and resource ('Read a generation's status, outputs, or failure details'), so the agent knows exactly what data it returns. It does not distinguish this generic fetch from siblings such as get_image, get_video, or get_audio, which is the only thing keeping it from a 5.

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?

Usage is only implied: polling after a generate_* call, or waiting via the wait/timeout parameters. There is no explicit statement of when to call this versus a type-specific getter, nor any guidance on when to poll repeatedly instead of using wait.

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