Skip to main content
Glama
MeiGen AI Design MCP

MeiGen AI Design MCP

check_generation

Idempotent

Checks an existing image or video generation job by generation ID or request ID without new charges, returning structured status and the next action to take after a lost or uncertain submit response.

Instructions

Read an existing MeiGen job without new charges. Provide generationId OR the caller requestId UUID. requestId lookup works after a lost submit response, process restart or another host. Follow structured status and nextAction; do not turn an uncertain status into a new paid UUID.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdNoOriginal workflow step UUID supplied to generate_image/video; authenticated lookup across hosts. Provide exactly one identifier.
generationIdNoAccepted generation ID. Provide exactly one of generationId and requestId.
requestedMediaTypeNoOriginal workflow step intent, when known. Preserve it from nextAction.arguments to detect a completed result of the other media type; this does not change or resubmit the job.

Output Schema

NameRequiredDescriptionDefault
urlsYes
errorNo
statusYes
dedupedNo
modelIdNo
successYes
imageUrlNo
providerNo
videoUrlNo
mediaTypeNo
requestIdNo
savedPathNo
nextActionNo
creditsUsedNo
generationIdNo
vectorOutputNo
creditsStatusNo
failureDetailNo
seedanceDraftNo
receiptWarningNo
downloadWarningNo
observationEndedNo
pollAfterSecondsNo
requestedMediaTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.4.0
    • changedOutput schema / properties / failureDetail / enum
      Previous value: -[
      -  "video_edit_duration",
      -  "reference_video_frame_rate"
      -]New value: +[
      +  "video_edit_duration",
      +  "reference_video_frame_rate",
      +  "midjourney_profile_not_found",
      +  "midjourney_sref_invalid"
      +]
    • addedOutput schema / properties / vectorOutput
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "height": {
      +      "maximum": 4096,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "url": {
      +      "format": "uri",
      +      "pattern": "^https:\\/\\/images\\.meigen\\.(?:ai|art)\\/[A-Za-z0-9_./-]+\\.svg$",
      +      "type": "string"
      +    },
      +    "width": {
      +      "maximum": 4096,
      +      "minimum": 1,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "url",
      +    "width",
      +    "height"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changedv3.3.0
    • addedOutput schema / properties / failureDetail
      Added value: +{
      +  "enum": [
      +    "video_edit_duration",
      +    "reference_video_frame_rate"
      +  ],
      +  "type": "string"
      +}
  3. Changed1 schema field changedv3.2.0
    • addedOutput schema / properties / seedanceDraft
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "duration": {
      +      "type": "number"
      +    },
      +    "expiresAt": {
      +      "type": "string"
      +    },
      +    "finalCredits": {
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    "finalGenerationId": {
      +      "type": "string"
      +    },
      +    "hasReferenceVideo": {
      +      "type": "boolean"
      +    },
      +    "referenceVideoSeconds": {
      +      "type": "number"
      +    },
      +    "sourceGenerationId": {
      +      "type": "string"
      +    },
      +    "stage": {
      +      "enum": [
      +        "draft",
      +        "final"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "stage",
      +    "duration",
      +    "referenceVideoSeconds",
      +    "hasReferenceVideo"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changedv3.1.0
    • changedOutput schema / properties / provider / enum
      Previous value: -[
      -  "meigen",
      -  "openai",
      -  "comfyui"
      -]New value: +[
      +  "meigen",
      +  "openai"
      +]
  5. Addedv2.0.1

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description reinforces that with the 'no new charges' guarantee and the cross-host lookup semantics, which is real added context. However, readOnlyHint=false is left unexplained against a description that frames the operation as a pure read; an agent is not told whether the lookup records or mutates anything server-side.

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?

Three tight sentences, front-loaded with the read/scope statement and the identifier rule before the recovery guidance. Nearly every clause carries information; only the trailing warning is slightly repetitive of 'without new charges.'

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 it correctly points the agent at structured status and nextAction instead. What remains missing is only the reason for readOnlyHint=false, which prevents a full score.

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 coverage is 100%, so all three parameters are already documented, including the mutual exclusivity of generationId and requestId. The description adds only the rationale for the requestId path (lost response, restart, other host), which is useful but does not exceed the schema baseline.

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?

Opens with a specific verb and resource: 'Read an existing MeiGen job.' The phrases 'without new charges' and 'do not turn an uncertain status into a new paid UUID' implicitly separate it from the paid generate_image/generate_video siblings, so an agent can tell which family this belongs to.

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 states when the requestId path applies — after a lost submit response, a process restart, or from another host — which is exactly the recovery scenario an agent needs. It also states when NOT to use the paid alternative, closing the loop with a clear exclusion.

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