Skip to main content
Glama

Generate an image

image_generate

Starts an EdgeCloud image generation from a prompt and returns the image. Charges credits per image, only on success; price it with quote. Needs sign-in (auth_challenge then auth_verify).

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

Input Schema

NameRequiredDescriptionDefault
sizeNoImage size in px (512 only)
promptYesWhat to draw, up to 1,000 characters
quote_idNoThe quote_id returned by quote (valid 5 minutes, single use). Use instead of max_price_credits
max_price_creditsNoThe most you'll pay for this call, in Wave credits. Needed unless you pass quote_id; the call fails if the price is higher

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / max_price_credits / description
      Previous value: -"The most you'll pay, in credits"New value: +"The most you'll pay for this call, in Wave credits. Needed unless you pass quote_id; the call fails if the price is higher"
    • addedInput schema / properties / max_price_credits / minimum
      Added value: +0
    • addedInput schema / properties / prompt / description
      Added value: +"What to draw, up to 1,000 characters"
    • addedInput schema / properties / quote_id / description
      Added value: +"The quote_id returned by quote (valid 5 minutes, single use). Use instead of max_price_credits"
    • addedInput schema / properties / size / default
      Added value: +512
    • addedInput schema / properties / size / description
      Added value: +"Image size in px (512 only)"
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (which only say it is a non-readonly, open-world, non-idempotent, non-destructive operation), the description discloses the credit charge per image, that billing occurs only on success, and the required auth sequence. These are exactly the operational facts an agent needs before spending money, and none are duplicated from the annotation block.

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 short sentences, front-loaded with the action and outcome, then cost, then auth. Dense and mostly waste-free, though 'Starts ... and returns the image' is mildly redundant phrasing rather than a crisp verb-object statement.

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?

With no output schema, the description correctly states the tool returns the image directly, and it covers the two silent failure modes an agent would otherwise hit (unauthenticated, unpriced). Failure behavior for a denied or unaffordable call is only partially implied, keeping it short of a 5.

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 size, prompt, quote_id, and max_price_credits are already fully documented with formats, limits, and a 5-minute single-use validity note. The description only restates the quote linkage ('price it with quote'), adding no syntax or trade-off detail beyond the schema; baseline 3 applies.

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 verb and resource: it starts an EdgeCloud image generation from a prompt and returns the resulting image. It is clear what the tool produces, though it does not explicitly contrast with a hypothetical alternative image tool (only with the pricing sibling, quote).

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 real preconditions: sign-in via auth_challenge then auth_verify, and pricing via quote before committing to a paid call. That is clear when-to-use and prerequisite guidance, but there is no explicit when-not-to-use or statement of what happens if the caller skips the quote path.

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