Skip to main content
Glama

GenMagic

by io.github.yumaheymans
OverviewDiscussionsAdmin

Generate text

generate_text

Generate text with GenMagic: copy, an answer, a draft, code, an SVG graphic, or a complete web page. Pass 'type' to make a specific artifact ("website" for a full self-contained HTML page, "svg" for a vector graphic, "code" for a code snippet, "writing" for prose); omit it for plain text. Attach files for the model to read via 'attachments' (PDF, Word/Excel/PowerPoint, CSV, text/code, images, audio); GenMagic converts anything a model cannot ingest natively. If the caller's account has brand personalization on, the output comes out on-brand automatically, and a website or svg also picks up the brand's palette and typeface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoThe kind of artifact to make. Omit for plain text.
modelNoOptional GenMagic model id for the text (call list_models with category "text" for the ids and prices). Omit it to let GenMagic choose its default.
promptYesWhat to write or produce.
systemNoOptional system instruction to steer tone, role, or format.
attachmentsNoFiles for the model to read. Each item is { name, mime, dataUrl } where dataUrl is a base64 data URL (data:<mime>;base64,...). Any type is accepted: PDF, docx/xlsx/pptx, csv, text/code, images, audio.

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 text (call list_models with category \"text\" for the ids and prices). Omit it to let GenMagic choose its default.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, so the description carries the full burden. It discloses useful behaviors: attachment conversion for non-ingestible formats, automatic brand personalization affecting output palette/typeface, and default model selection. Does not cover rate limits, auth, or failure modes.

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?

Front-loaded with purpose and artifact types, then attachments, then brand behavior. Three sentences with no obvious filler, though the brand paragraph is somewhat tangential.

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?

Covers the key behaviors an agent needs: artifact type routing, attachment handling, brand personalization. Lacks explicit mention of what happens with the 'model' parameter default beyond what schema says, but overall complete for a generation tool with no output schema.

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 already 100%, so baseline is 3, but the description adds value by explaining the semantic effect of 'type' values and the attachment auto-conversion behavior beyond raw schema descriptions.

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 (generate) and resource (text) and enumerates the artifact types it can produce. Distinguishes itself from siblings like generate_image and generate_speech by scoping to text and code/SVG/website artifacts.

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 for the 'type' parameter (use 'website'/'svg'/'code'/'writing' or omit for plain text). Doesn't explicitly compare to sibling tools like generate_image, but the artifact-type routing is strong.

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