Skip to main content
Glama
V-Songbird

gemini-relay

by V-Songbird
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gemini-image

Generate images from text descriptions, choose the aspect ratio and output resolution, and optionally save the result directly into your project.

Instructions

Generate images from text descriptions through the Antigravity CLI's image generation tool. Supports aspect ratio and output size selection, plus optional export directly into your project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoOptional output resolution ('512', '1K', '2K' or '4K'). Omit to let Gemini pick.
promptYesDetailed visual description of the image to create (subject, environment, lighting, artistic style, colors).
outputPathNoOptional path, relative to the project root, where the generated image should be copied (e.g., 'assets/hero.jpg'). A path escaping the project root is refused.
aspectRatioNoAspect ratio of the generated image (default: '1:1').1:1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • changedInput schema / properties / aspectRatio / enum
      Previous value: -[
-  "1:1",
-  "16:9",
-  "9:16",
-  "4:3",
-  "3:4",
-  "3:2",
-  "2:3"
-]New value: +[
+  "1:1",
+  "16:9",
+  "9:16",
+  "4:3",
+  "3:4",
+  "3:2",
+  "2:3",
+  "5:4",
+  "4:5",
+  "21:9",
+  "4:1",
+  "1:4",
+  "8:1",
+  "1:8"
+]
    • changedInput schema / properties / outputPath / description
      Previous value: -"Optional relative file path in your project workspace where the generated image file should be copied (e.g., 'assets/hero.jpg')."New value: +"Optional path, relative to the project root, where the generated image should be copied (e.g., 'assets/hero.jpg'). A path escaping the project root is refused."
    • addedInput schema / properties / size
      Added value: +{
+  "description": "Optional output resolution ('512', '1K', '2K' or '4K'). Omit to let Gemini pick.",
+  "enum": [
+    "512",
+    "1K",
+    "2K",
+    "4K"
+  ],
+  "type": "string"
+}
  2. First observedv1.2.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose a material side effect: optional export directly into the project, and it places the tool in the Antigravity CLI context. However, it does not mention overwrite behavior, what happens when outputPath is omitted, or generation failure modes, leaving some behavioral gaps.

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 with no filler. The first sentence states the core purpose, and the second compactly lists the key options. Information is front-loaded and every word earns its place.

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 the 100% schema coverage and straightforward nature of image generation, the tool definition is largely complete: prompt, sizes, aspect ratios, and export path are all documented. The only notable gap is the lack of any statement about what the tool returns when outputPath is omitted, which matters more because there is no output schema.

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 the baseline is 3. The description's second sentence ('Supports aspect ratio and output size selection, plus optional export') merely summarizes the schema's parameters without adding new meaning; the schema itself already documents each parameter precisely.

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?

The description opens with a specific verb phrase 'Generate images from text descriptions', naming the resource (image generation) and the input (text). It also names the context 'Antigravity CLI's image generation tool' and the supported options, clearly distinguishing it from the chat/planning sibling tools.

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?

The intended use is clear from the first sentence: generate an image when you have a text description. The description also previews optional export, helping an agent infer workflow use. It does not explicitly name alternatives, but no sibling tool performs image generation, so the context is unambiguous.

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