Clipia

get_generation

Read-onlyIdempotent

Get the current status/result of a generation without waiting. When COMPLETED, output.images[].url is the inline webp preview and output.images[].original_url is the full-quality PNG/JPG.

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": {
      "request_id": "<request_id>"
    },
    "name": "get_generation"
  }
}

Input Schema

Name	Required	Description	Default
`request_id`	Yes
`include_preview`	No

Output Schema

Name	Required	Description
`error`	No
`model`	Yes
`stage`	Yes
`output`	Yes
`status`	Yes
`version`	Yes
`progress`	Yes
`snapshot`	Yes
`terminal`	Yes
`warnings`	No	Execution notices for this request. Absent when there are none. Example: code "audio_dropped" — the audio track did not pass the safety check of the model, so the video has no sound; the price is unchanged. Skip codes you do not know.
`next_step`	No
`created_at`	Yes
`media_kind`	Yes
`request_id`	Yes
`completed_at`	Yes
`cost_credits`	No
`next_poll_ms`	Yes
`schema_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine value by explaining that COMPLETED results carry both an inline webp preview URL and a separate full-quality original_url — a distinction not obvious from field names alone.

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 sentences, no filler, with the core action front-loaded and the result-shape detail second. Nothing in it is wasted.

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

Completeness3/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 need not be fully re-described, and the description covers the COMPLETED case reasonably. But it never addresses non-completed states (pending/failed), polling cadence, or what happens with an unknown request_id — gaps that matter for a status-polling tool.

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

Parameters2/5

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

Schema description coverage is 0% and neither parameter is explained in the description. In particular, include_preview (defaulting to true) is left undefined — an agent cannot tell whether setting it false suppresses the preview URL or the whole image payload, which directly interacts with the sentence about output.images[].

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+resource (get the status/result of a generation) and adds the scope qualifier 'without waiting,' which implicitly separates it from the wait_generation sibling. An agent can tell what this does and roughly how it differs from the blocking alternative 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 Guidelines3/5

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

'Without waiting' hints that this is the non-blocking/polling variant versus wait_generation, but the description never names that alternative or states when to poll again vs. block, nor how long results remain retrievable. Usage is implied rather than prescribed.

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

All Clipia 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.