Skip to main content
Glama

Generate Image

generate_image

Create images with HalalGen (the prompt is checked against HalalGen's content rules first: people and animals get a smooth face with no features). 'Auto' uses GPTImage25Flare on paid plans and CF_Flux2Klein on the free plan. Free plan: CF_Flux2Klein and CF_Flux2Dev only. Returns the image URL; share it with the user. To change one of the user's own pictures, use edit_image instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "generate_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoImage model. Call list_models for costs.Auto
promptYesWhat to create. Describe the scene, lighting, materials and mood. Avoid faces. Looks from HalalGen's templates can be asked for here too, for example one object seen from several camera angles, a faceless cartoon-style character, or exercise steps shown with silhouettes.
qualityNoUsed by GPT Image 2.6 and 2.5 only: hd and ultra cost more (list_models shows each price). Flux Ultra and Flux 2.0 Pro are always ultra; other models are standard.standard
is_privateNoKeep the image out of the public gallery. Needs a paid plan.
num_imagesNoHow many images. The free plan makes one; paid plans up to 4.
aspect_ratioNoImage shape.16:9
movement_typeNoOptional camera framing hint added to the prompt.
cinematic_styleNoOptional style preset added to the prompt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / model / enum
      Previous value: -[
      -  "Auto",
      -  "CF_Flux2Klein",
      -  "CF_Flux2Dev",
      -  "GPTImage25Flare",
      -  "GPTImage25Sunburst",
      -  "GPTImage2",
      -  "Flux20Pro",
      -  "FluxPro",
      -  "FluxUltra",
      -  "StabilityUltra",
      -  "Seedream40"
      -]New value: +[
      +  "Auto",
      +  "CF_Flux2Klein",
      +  "CF_Flux2Dev",
      +  "GPTImage26Flare",
      +  "GPTImage26Sunburst",
      +  "GPTImage25Flare",
      +  "GPTImage25Sunburst",
      +  "GPTImage2",
      +  "Flux20Pro",
      +  "FluxPro",
      +  "FluxUltra",
      +  "StabilityUltra",
      +  "Seedream40"
      +]
    • changedInput schema / properties / quality / description
      Previous value: -"Used by GPT Image 2.5 only: hd and ultra cost more (list_models shows each price). Flux Ultra and Flux 2.0 Pro are always ultra; other models are standard."New value: +"Used by GPT Image 2.6 and 2.5 only: hd and ultra cost more (list_models shows each price). Flux Ultra and Flux 2.0 Pro are always ultra; other models are standard."
  2. Changed1 schema field changed
    • removedInput schema / properties / relaxed_mode
      Removed value: -{
      -  "default": false,
      -  "description": "Queue without spending credits. Iltizam and Ihsan plans only.",
      -  "type": "boolean"
      -}
  3. Changed2 schema fields changed
    • changedInput schema / properties / is_private / description
      Previous value: -"Keep the image private in the user's Vault."New value: +"Keep the image out of the public gallery. Needs a paid plan."
    • changedInput schema / properties / num_images / description
      Previous value: -"How many images (paid plans: up to 4)."New value: +"How many images. The free plan makes one; paid plans up to 4."
  4. Changed1 schema field changed
    • changedInput schema / properties / quality / description
      Previous value: -"Used by GPT Image 2.5 only: hd costs ×1.2, ultra ×1.8. Flux Ultra and Flux 2.0 Pro are always ultra; other models are standard."New value: +"Used by GPT Image 2.5 only: hd and ultra cost more (list_models shows each price). Flux Ultra and Flux 2.0 Pro are always ultra; other models are standard."
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The annotations only declare that the tool is a non-read-only, open-world, non-idempotent, non-destructive operation. The description adds substantial context beyond that: prompts are moderated against content rules, faces are smoothed and featureless, model selection depends on plan tier, and the tool returns a shareable image URL. Those are non-obvious side effects and constraints an agent cannot infer from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description front-loads the core action and moderation caveat, then moves to model/plan routing and the edit_image redirect. It is dense and useful, though the parenthetical face-smoothing note and the Auto-routing sentence could be tightened.

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 generation tool with no output schema, the description covers return value (image URL, share with user), content policy, and plan gating. It does not address cost implications directly beyond deferring to list_models, nor latency/queuing behavior, but nothing essential to calling the tool correctly is missing.

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 plan-dependent meaning the schema does not: Auto routes to GPTImage25Flare on paid plans and CF_Flux2Klein on free, and num_images is effectively capped at 1 on the free plan. Minor naming drift exists (the description mentions GPTImage25Flare while the schema enum also lists GPTImage26Flare, and the schema lists Flux20Pro while the quality text says "Flux 2.0 Pro"), which slightly weakens precision.

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 opens with a specific verb+resource ("Create images with HalalGen") and immediately distinguishes itself from the sibling edit_image, which handles modification of the user's own pictures. An agent can tell which tool to select without opening either schema.

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?

It gives an explicit routing rule: for changing one of the user's own pictures, use edit_image instead. It also states plan-conditioned usage (free plan limited to CF_Flux2Klein and CF_Flux2Dev), but it does not clarify when this tool is preferable to generate_logo, generate_video, or other image-producing siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources