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

TableJSON 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

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful behavior: output is returned inline plus a hosted URL, and brand personalization applies automatically when enabled. It does not address auth/permissions, cost/credit consumption, or rate limits, which are material for a generation tool.

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?

A single compact cluster of sentences with the core generation behavior front-loaded and the mode-switching clauses following. Nearly every clause earns its place; the brand-personalization sentence at the end is slightly peripheral but still informative.

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?

There is no output schema, so the description's statement of the return format (inline image + hosted URL) is genuinely valuable. It covers all three usage modes and the model-selection path, leaving only auth and cost details unaddressed.

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 all five parameters are already documented in the schema. The description reinforces the semantics of 'image' (image-to-image) and 'type' ('logo'), but adds little beyond what the schema states, so the 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?

States a specific verb+resource (generate an image from a text description) and immediately distinguishes three modes: text-to-image, image-to-image via the 'image' param, and logo generation via 'logo'. An agent can tell it apart from create_video, generate_music, and the other siblings without opening schemas.

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?

Gives clear conditional guidance: pass 'image' to transform rather than generate, and set type 'logo' for a brand mark. It also routes the agent to list_models for model ids and prices. It stops short of stating when NOT to use it or naming a sibling alternative explicitly.

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