Skip to main content
Glama
eyaeya

relay-image-mcp

by eyaeya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

generate_image

Generate or edit a single image via a configurable relay, applying explicit output parameters and verifying the returned bytes meet the requested constraints.

Instructions

Generate or edit one image through the configured relay; send explicit output parameters and verify original returned bytes. No retries, resizing, model substitution or fallback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoauto edits when references exist; generate uses references as inspiration. edit requires an input image.auto
sizeNomax, auto, source, or WIDTHxHEIGHT. Max resolves the largest documented legal request canvas. Returned dimensions are checked; no resampling.max
promptYes
strictNoReturn isError when requested constraints are unmet or model/quality metadata is insufficient; keep image and report.
qualityNoExplicit quality field. Higher levels require model support; returned metadata is checked separately from visual quality.high
preserveNoContent that must remain unchanged when editing; requires visual review.
backgroundNoauto, opaque or transparent. Real alpha pixels are inspected after full decoding.auto
image_modelNoExplicit image model; availability and supported quality depend on the provider. No automatic substitution.gpt-image-2.5-sunburst
aspect_ratioNoauto, source, or W:H e.g. 16:9, 9:16, 1:1. Must agree with explicit size. API derives a compatible size. Checked against actual output.auto
output_formatNoPNG, WebP or JPEG; transparent output requires PNG or WebP. Actual file format is verified.png
reference_rolesNoOne role per input image in order, e.g. edit target, lighting reference, object to insert.
reference_image_pathsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.3
    • changedInput schema / properties / image_model / default
      Previous value: -"gpt-image-2"New value: +"gpt-image-2.5-sunburst"
  2. First observedv0.3.2

TDQS

A4/5.0
Behavior4/5

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

The description adds genuine behavioral claims beyond the annotations: no retries, no resizing, no model substitution, no fallback, and a requirement to verify the original returned bytes. Annotations already provide read-only, destructive, and idempotency hints, so these extra details meaningfully inform the agent without repeating structured data.

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?

Two sentences, no waste: the first gives the core purpose, the second and third consolidate the critical behavioral contract. Every clause earns its place and it does not duplicate schema-defined parameter details.

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?

Given 12 parameters, no output schema, and annotations that already describe side effects, the description is enough to guide the agent at a high level, but does not fully cover what to know about the return value or when to prefer this tool over the sibling inspection/status tools. Overall, the main missing piece is selection routing, which is only a minor completeness gap.

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?

With 83% schema description coverage, the individual parameter descriptions already carry most of the semantic weight. The description provides a general instruction to set explicit output parameters and verify returned bytes, which touches several related properties but does not compensate for the few undocumented schema items (e.g., prompt, reference_image_paths).

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 the exact operation: 'generate or edit' the resource 'one image'. It is immediately distinct from the siblings inspect_image (inspection) and status (service state), so an agent can tell this tool apart 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 Guidelines3/5

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

The intended purpose is implied clearly: use this when you need to generate or edit an image. However, there is no explicit when-to-use versus when-not-to-use guidance and the sibling tools are not referenced for comparison. The added constraints are about tool behavior, not selection strategy.

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

Deploy Server

Other Tools