Skip to main content
Glama

Image Generation

images
Read-only

Generate images from text prompts. Returns a hosted URL of the image and the same image as base64 (b64_json), with its content_type (image/png or image/jpeg, as the bytes are), the aspect ratio and the size used. Use to create a new picture from a description. To cut the background out of an existing image use bg-remove; to capture a web page use screenshot. Cost: 512px 1 credit, 1K 2 credits, 2K 3 credits, 4K 5 credits, charged only when a call succeeds.

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": "images"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesImage description.
image_sizeNoImage size: the longer side, about 512, 1024, 2048 or 3840 pixels. The price depends on it.512px
aspect_ratioNoAspect ratio.1:1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / image_size / description
      Previous value: -"Image size: the longer side, about 512, 1024, 2048 or 4096 pixels. The price depends on it."New value: +"Image size: the longer side, about 512, 1024, 2048 or 3840 pixels. The price depends on it."
  2. Changed1 schema field changed
    • addedInput schema / properties / image_size
      Added value: +{
      +  "default": "512px",
      +  "description": "Image size: the longer side, about 512, 1024, 2048 or 4096 pixels. The price depends on it.",
      +  "enum": [
      +    "512px",
      +    "1K",
      +    "2K",
      +    "4K"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld false and non-destructive; the description goes well beyond that by disclosing the return payload (hosted URL plus b64_json with content_type) and a per-resolution credit cost with the important guarantee that charges happen only on success. Cost and billing semantics are exactly the behavioral context annotations cannot express.

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, then returns, then routing, then cost — a sensible order with no filler. The cost clause is dense but earns its place; the only mild redundancy is re-describing output fields the caller will see anyway.

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 carries the return-value burden and does so concretely: URL, base64, content_type values, aspect ratio and size actually used. Combined with the cost model and sibling routing, an agent has everything needed to call this correctly and predict the result.

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 3 is the baseline, and the description adds real value by tying price to the image_size parameter (512px 1 credit through 4K 5 credits) rather than restating enum meanings. It adds nothing about aspect_ratio beyond the schema's own enum, which keeps it below a 5.

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 ("Generate images from text prompts") and immediately distinguishes the tool from adjacent ones by naming bg-remove and screenshot as the tools for background removal and page capture. An agent can tell text-to-image apart from the rest of the catalog without inspecting any 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 a clear when-to-use line ("Use to create a new picture from a description") and routes two adjacent tasks to siblings with explicit conditions. It stops short of exclusions for near-miss cases such as editing or restyling an existing image, so it is strong context rather than a complete decision rule.

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.