Skip to main content
Glama

CreateHQ Image Studio

generate_image

Any picture from a description in your own words — a product shot, an illustration, a poster, a scene — following up to three reference photos for the subject or the style. The description goes in prompt, 800 characters at most. Up to 3 pictures per call. Costs 2 credits per picture (4 for HD) from the connected account.

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
countNoHow many pictures, one credit draw each.
ratioNoDefault 1:1.
promptYesWhat the picture should be, in your own words.
qualityNoHD doubles the credit cost.
referencesNoUp to 3 pictures as data URLs, for the subject or the style to follow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations at all, the description carries the full behavioral burden and does a solid job on the commercial side: it discloses that credits are drawn from the connected account, that standard costs 2 credits per picture and HD costs 4, and that up to 3 pictures are produced per call. It stops short of describing what comes back (URLs, data, async job) or what happens on failure/refund, which matters given the credit cost.

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?

Three tight sentences that front-load the core capability before moving to constraints and cost. There is minor redundancy — the 800-character prompt limit and the 3-per-call cap are each stated where the schema already says them — but nothing is wasted or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description is the only source of truth, and it never says what the tool returns (image URLs, base64, references to stored assets) or how to handle partial failures. Cost, count, and reference limits are well covered, making it adequate but not complete for a credit-consuming generative tool.

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 coverage is 100%, so the schema already documents every parameter, and the description mostly restates it — the 800-character prompt limit, the 3-picture cap, and the HD cost doubling all appear in the schema descriptions. It adds the useful framing that references are 'for the subject or the style', but the `ratio` parameter is never mentioned in the description at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope — 'Any picture from a description in your own words' with concrete examples (product shot, illustration, poster, scene) — so the agent knows this is a general-purpose text-to-image generator. It does not name or contrast with the sibling image tools (creator_cover, pet_holiday_portraits), leaving the general-vs-specialized routing to be inferred from the word 'Any'.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'Any picture' suggests this is the catch-all option and the examples hint at the kinds of requests it fits. There is no explicit when-to-use/when-not-to-use guidance and no mention of the sibling tools as alternatives for covers or portraits, nor any prerequisites such as the connected account being required.

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