Kuro

Get generation

get_generation

Read-onlyIdempotent

Get current status and signed media URL for one generation. A generate tool answers with a quick image already finished and with anything slower at once. For a row still queued or generating, call this once: it waits up to 40 seconds and answers the moment the generation is ready or failed. Call it again only while the status is still queued or generating; ready_in_seconds says roughly how long is left. wait_seconds: 0 reads the status without waiting. include adds detail the plain read leaves out: attempts — every attempt behind a retried row, newest first — and members, the generations inside a group (refused on a row that is not a group).

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

Input Schema

Name	Required	Description	Default
`include`	No
`wait_seconds`	No
`generation_id`	Yes

Output Schema

Name	Required	Description
`members`	No
`message`	Yes
`attempts`	No
`generation`	Yes	One image, clip, voice-over or piece of music.
`group_size`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedNov 4, 2026

addedOutput schema / properties / generation / description

Added value: +"One image, clip, voice-over or piece of music."

addedOutput schema / properties / generation / properties / app_url / description
```
Added value: +"Opens it in the app."
```
addedOutput schema / properties / generation / properties / aspect_ratio / description
```
Added value: +"Null for audio."
```
addedOutput schema / properties / generation / properties / created_at / format
```
Added value: +"date-time"
```

addedOutput schema / properties / generation / properties / credits

Added value: +{
+  "description": "Credits charged. Zero when your own provider key or the free allowance paid.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

removedOutput schema / properties / generation / properties / credits_cost
```
Removed value: -{
-  "type": [
-    "number",
-    "null"
-  ]
-}
```
addedOutput schema / properties / generation / properties / error / description
```
Added value: +"Why it failed. Null otherwise."
```
removedOutput schema / properties / generation / properties / generation_id
```
Removed value: -{
-  "format": "uuid",
-  "type": "string"
-}
```

addedOutput schema / properties / generation / properties / id

Added value: +{
+  "format": "uuid",
+  "type": "string"
+}

removedOutput schema / properties / generation / properties / kind

Removed value: -{
-  "enum": [
-    "image",
-    "video",
-    "audio",
-    "tool"
-  ],
-  "type": "string"
-}

addedOutput schema / properties / generation / properties / model / description
```
Added value: +"The model id it was made with (`GET /v1/models`)."
```

addedOutput schema / properties / generation / properties / object

Added value: +{
+  "const": "generation",
+  "type": "string"
+}

addedOutput schema / properties / generation / properties / output_url / description

Added value: +"The finished file, once `ready`. A signed link that works for about an hour; read the generation again for a fresh one."

addedOutput schema / properties / generation / properties / paid_by / description

Added value: +"Who paid: \"credits\", \"house\" (the free allowance), \"server\" (a server that charges nothing), or the vendor of your own key (\"replicate\", \"fal\", …)."

addedOutput schema / properties / generation / properties / ready_in_seconds / description

Added value: +"Roughly how long an unfinished generation has left; 0 means past its usual time."

addedOutput schema / properties / generation / properties / recipe_id

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/properties/generation/properties/id"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The recipe it was made with, if any."
+}

addedOutput schema / properties / generation / properties / status / description
```
Added value: +"`ready` and `failed` are final."
```

addedOutput schema / properties / generation / properties / thumbnail_url

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/properties/generation/properties/output_url/anyOf/0"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "A small still of the result, for a grid. Null for audio and while it works."
+}

addedOutput schema / properties / generation / properties / type

Added value: +{
+  "description": "What was made. New values may be added; treat an unknown one as opaque.",
+  "enum": [
+    "image",
+    "clip",
+    "voiceover",
+    "music",
+    "tool"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / generation / required

Previous value: -[
-  "generation_id",
-  "kind",
-  "status",
-  "model",
-  "prompt",
-  "aspect_ratio",
-  "refined_from",
-  "caption_style",
-  "output_url",
-  "credits_cost",
-  "paid_by",
-  "error",
-  "vendor_phase",
-  "stalled",
-  "ready_in_seconds",
-  "created_at",
-  "app_url"
-]New value: +[
+  "object",
+  "id",
+  "type",
+  "status",
+  "model",
+  "prompt",
+  "aspect_ratio",
+  "output_url",
+  "thumbnail_url",
+  "credits",
+  "paid_by",
+  "error",
+  "ready_in_seconds",
+  "recipe_id",
+  "created_at",
+  "app_url",
+  "refined_from",
+  "caption_style",
+  "vendor_phase",
+  "stalled"
+]

Changed2 schema fields changedOct 26, 2026

addedOutput schema / properties / generation / properties / paid_by
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changedOutput schema / properties / generation / required

Previous value: -[
-  "generation_id",
-  "kind",
-  "status",
-  "model",
-  "prompt",
-  "aspect_ratio",
-  "refined_from",
-  "caption_style",
-  "output_url",
-  "credits_cost",
-  "error",
-  "vendor_phase",
-  "stalled",
-  "ready_in_seconds",
-  "created_at",
-  "app_url"
-]New value: +[
+  "generation_id",
+  "kind",
+  "status",
+  "model",
+  "prompt",
+  "aspect_ratio",
+  "refined_from",
+  "caption_style",
+  "output_url",
+  "credits_cost",
+  "paid_by",
+  "error",
+  "vendor_phase",
+  "stalled",
+  "ready_in_seconds",
+  "created_at",
+  "app_url"
+]

Changed3 schema fields changedOct 21, 2026

addedInput schema / properties / wait_seconds

Added value: +{
+  "maximum": 40,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / generation / properties / ready_in_seconds
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```

changedOutput schema / properties / generation / required

Previous value: -[
-  "generation_id",
-  "kind",
-  "status",
-  "model",
-  "prompt",
-  "aspect_ratio",
-  "refined_from",
-  "caption_style",
-  "output_url",
-  "credits_cost",
-  "error",
-  "vendor_phase",
-  "stalled",
-  "created_at",
-  "app_url"
-]New value: +[
+  "generation_id",
+  "kind",
+  "status",
+  "model",
+  "prompt",
+  "aspect_ratio",
+  "refined_from",
+  "caption_style",
+  "output_url",
+  "credits_cost",
+  "error",
+  "vendor_phase",
+  "stalled",
+  "ready_in_seconds",
+  "created_at",
+  "app_url"
+]

First observedOct 15, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses the long-poll behavior (waits up to 40 seconds, returns the moment the row is ready or failed), the retry-exit condition, the ready_in_seconds hint, and that `members` is refused on non-group rows. What's missing is any note on error behavior for an unknown/deleted id or whether the signed URL expires.

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?

Front-loaded with the core purpose, then polling rules, then optional parameters, in that priority order. Dense but nearly every clause adds operational value; the sentence about generate tools returning quick images is slightly convoluted but justifies the polling model.

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?

An output schema exists, so return values needn't be spelled out, and the description still names the key fields (status, signed media URL, ready_in_seconds). For a read-only long-poll tool with three parameters, an agent has everything needed to call it correctly and to know when to stop.

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 description coverage is 0%, so the description carries the burden and mostly does: `include` values are explained with meaning and a failure mode, `wait_seconds: 0` gets a concrete semantic, and the 40-second cap is implied. generation_id is left uninterpreted (its UUID format is only in the schema), which is the one gap.

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?

States a specific verb and resource ('Get current status and signed media URL for one generation'), which distinguishes it immediately from list_generations (many rows) and get_download_url (URL only). The addition of the polling/wait semantics further separates it from plain read siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly explains the relationship with the generate tools (they return fast images, slower work must be polled), instructs to call once and only re-call while status is queued/generating, and names wait_seconds: 0 as the no-wait alternative. When-to-use, when-to-stop, and the sibling alternative are all covered.

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

All Kuro tools Inspect

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

Need Help?