MeiGen AI Image Generation MCP

Overview Schema Source Related Servers Discussions Admin

list_models

Read-only

List available AI image generation models and their capabilities to compare options and select the right one. Filter to active models by setting activeOnly.

Instructions

List available AI image generation models and their capabilities. For up-to-date pricing, see https://www.meigen.ai/model-comparison.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`activeOnly`	No	Only show active models (default: true)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`models`	Yes
`success`	Yes
`configuredProviders`	Yes
`executionCapabilities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.1Sep 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "configuredProviders": {
+      "items": {
+        "enum": [
+          "meigen",
+          "openai",
+          "comfyui"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "error": {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retryable": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "code",
+        "message",
+        "retryable"
+      ],
+      "type": "object"
+    },
+    "executionCapabilities": {
+      "additionalProperties": false,
+      "properties": {
+        "concurrency": {
+          "type": "string"
+        },
+        "download": {
+          "type": "boolean"
+        },
+        "maxConcurrentSubmissions": {
+          "type": "number"
+        },
+        "submitOnly": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "submitOnly",
+        "download",
+        "maxConcurrentSubmissions",
+        "concurrency"
+      ],
+      "type": "object"
+    },
+    "models": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "models",
+    "configuredProviders",
+    "executionCapabilities"
+  ],
+  "type": "object"
+}

Addedv1.3.1May 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds the context that it lists models and their capabilities, and points to an external URL for up-to-date pricing, which is useful. It doesn't describe pagination or response format, but the output schema exists to cover that.

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 with no waste. The core purpose is front-loaded, and the pricing link is a useful addition that doesn't clutter the description.

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?

For a simple read-only list tool with one optional parameter and an output schema, the description is nearly complete. The only minor gap is not explicitly stating that it returns a list of models with capabilities, but that's implied by 'List available AI image generation models and their capabilities.'

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 the schema already documents the activeOnly parameter. The description doesn't add much beyond the schema, but it does mention 'capabilities' which hints at what the output contains. Baseline 3 is appropriate.

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?

The description clearly states the tool lists available AI image generation models and their capabilities, which is a specific verb+resource. It distinguishes itself from siblings like list_skills by explicitly scoping to AI image generation models.

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?

The description implies usage for discovering available models and capabilities, and the activeOnly parameter provides context for filtering. However, it doesn't explicitly state when to use this tool versus alternatives like list_skills or check_skill, nor does it mention exclusions.

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

Deploy Server