Skip to main content
Glama

Generate a picture

generate_image

Generates one to four pictures with a genframe model and charges the account's credits (price per picture is in list_models; failed pictures are refunded). Returns the picture(s) and download links. Waits up to about 50 seconds; if a picture is still in progress, the result gives its job_id for get_job. Pictures with real people are allowed only as the person's own photos; the content policy of genframe.ai applies.

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
sizeNoSize option if the model has one, e.g. 1K, 2K, 4K (see list_models options.size).
countNoHow many pictures (each is charged). Default 1.
modelNoModel id from list_models. Default: a fast, cheap general model.
promptYesWhat to draw. Any language. 3–1500 characters.
qualityNoQuality option if the model has one (see list_models options.quality).
aspect_ratioNoFor example 1:1, 4:5, 9:16, 16:9, 3:2. The nearest ratio the model makes is used.
negative_promptNoWhat must not be in the picture (only models with negative: true).
reference_image_urlsNoOptional reference pictures: public https URLs (JPG, PNG, WebP up to 8 MB) or links returned by this server. Only for models with refMax > 0.
transparent_backgroundNoTransparent background (only models with alpha: true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say it is a non-read-only, non-idempotent, open-world write; the description adds real substance beyond that: credits are charged per picture, failed pictures are refunded, the call blocks for roughly 50 seconds, and in-progress results expose a job_id. The content-policy constraint on real people is a behavioral rule the agent could not infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Four compact sentences, front-loaded with the action and cost, then return shape, then async fallback, then policy. No filler and no repetition of schema text.

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?

There is no output schema, so the description correctly covers the return value ('the picture(s) and download links') and the partial-result path. For a nine-parameter, credit-charging generation tool, the cost, timing, policy, and follow-up behavior are all present.

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 nine parameters are already self-documenting; baseline is therefore 3. The description only adds a loose tie between the picture count and per-picture billing ('one to four pictures', 'price per picture'), without clarifying model/size/quality interactions the schema does not already cover.

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 and resource ('Generates one to four pictures with a genframe model'), plus the billing consequence. It also distinguishes itself from get_job (async continuation) and list_models (pricing/options), so an agent can place it in the flow without opening the 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?

Gives clear operating context: cost is looked up in list_models, unfinished generations route to get_job, and real-person photos are restricted to the subject's own images. It stops short of naming when a sibling such as generate_preset should be preferred over a freeform prompt, which keeps it from a 5.

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