Skip to main content
Glama

GenMagic

by io.github.yumaheymans
OverviewDiscussionsAdmin

Generate an image

generate_image

Generate an image from a text description with GenMagic. Pass 'image' (an https or data URL) to transform THAT image instead of generating from scratch (image-to-image), and type "logo" to make a brand mark. Returns the image inline plus a hosted URL. On-brand automatically when the account has brand personalization on.

Input Schema

NameRequiredDescriptionDefault
sizeNoImage size, e.g. 1024x1024 (square), 1792x1024 (wide), 1024x1792 (tall).
typeNoSet to 'logo' to generate a brand mark instead of a picture.
imageNoOptional reference image (an https URL or a data:image URL) to transform (image-to-image), e.g. a character to keep consistent.
modelNoOptional GenMagic model id for the image (call list_models with category "image" for the ids and prices). Omit it to let GenMagic choose its default.
promptYesA description of the image to create (or the edit to make when 'image' is given).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / model
      Added value: +{
+  "description": "Optional GenMagic model id for the image (call list_models with category \"image\" for the ids and prices). Omit it to let GenMagic choose its default.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-readonly, open-world, non-idempotent, non-destructive. The description adds real context beyond them: the return shape (inline image plus hosted URL) and an account-level side effect (output is on-brand when brand personalization is enabled). It omits cost/quotas, though it points at list_models for prices.

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?

Purpose and the default mode come first, then the two mode-switching caveats, then the return value. Dense and largely waste-free, though the trailing 'On-brand automatically...' clause is slightly compressed and reads as a run-on addition.

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?

No output schema exists, and the description compensates by stating what comes back (inline image plus hosted URL). With 5 params fully documented in schema, mode-switching explained, and model selection delegated to list_models, an agent has everything needed to call it correctly.

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 coverage is 100%, so the baseline is 3, but the description adds semantic framing the schema lacks: that 'image' switches the operation mode to image-to-image rather than being a mere optional field, and that 'type' controls logo vs picture. It does not restate size/model details, which the schema already covers.

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?

Specific verb + resource ('Generate an image from a text description with GenMagic') and it immediately distinguishes three modes: text-to-image, image-to-image (pass 'image'), and logo ('type "logo"'). An agent can tell this apart from generate_video/generate_music/generate_text by modality alone.

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

Usage Guidelines4/5

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

Explicit conditional guidance: pass 'image' to transform an existing image instead of generating from scratch, and set type 'logo' for a brand mark. It does not name sibling tools to route away from, but the modality split across siblings makes that unnecessary.

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

All GenMagic toolsInspect
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