Skip to main content
Glama
jau123

MeiGen AI Image Generation MCP

by jau123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

manage_preferences

Read or update machine-local defaults, style notes, and prompt bookmarks in ~/.config/meigen/preferences.json. These are not MeiGen account favorites or boards and do not sync across devices.

Instructions

Read or update machine-local defaults, style notes, and prompt bookmarks in ~/.config/meigen/preferences.json. These are not MeiGen account favorites or boards and do not sync across devices. Use only when the user requests local settings; use search_favorites and save_favorite for their MeiGen collection.

Input Schema

NameRequiredDescriptionDefault
indexNoremove_favorite: 0-based index of the favorite to remove
modelNoset: preferred default model name
styleNoset: preferred default style (e.g. "realistic", "anime", "illustration")
actionYesAction to perform: "get" reads all preferences, "set" updates defaults/styleNotes, "add_favorite" saves a prompt, "remove_favorite" removes by index
promptNoadd_favorite: the prompt text to save
providerNoset: preferred default provider
styleNotesNoset: free-text style notes (e.g. "cinematic lighting, shallow DOF, brand colors #1A1A2E")
aspectRatioNoset: preferred default aspect ratio. Use "auto" (recommended) to let MeiGen infer per-prompt, or pin a value like "16:9", "1:1", "9:16".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.0
    • changedInput schema / properties / provider / enum
      Previous value: -[
-  "openai",
-  "meigen",
-  "comfyui"
-]New value: +[
+  "openai",
+  "meigen"
+]
  2. Addedv1.3.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description carries most of the behavioral burden. It usefully discloses that state lives in ~/.config/meigen/preferences.json, is machine-local, and does not sync across devices. It does not describe write side effects beyond that, but the storage and sync semantics are valuable context beyond the annotations.

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?

Three tight sentences, front-loaded with the core purpose, followed by the scope clarification and the routing instruction. No filler; each sentence earns its place.

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 an 8-parameter get/set tool with minimal annotations and no output schema, the description conveys scope, storage location, persistence behavior, and alternatives. It stops short of describing what a 'get' returns or the effect of each write action, which is a minor gap given the schema covers parameters fully.

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 each parameter (including action enum, op-specific fields, aspectRatio 'auto' guidance) is already documented in the schema. The description names the categories of content (defaults, style notes, bookmarks) but adds no syntax or format detail beyond what the schema provides, so baseline 3 applies.

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 specific verbs (Read or update) plus the resource (machine-local defaults, style notes, prompt bookmarks) and even the storage file path. It clearly distinguishes this local-settings tool from account-scoped favorites/boards, so an agent can tell what it does without opening the schema.

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 scopes usage with 'Use only when the user requests local settings' and names the alternatives for the other case (search_favorites and save_favorite for the MeiGen collection). This gives both the when-to-use and the routing-away condition.

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

Deploy Server

Other Tools