Skip to main content
Glama

Vee3

by io.github.Vee3io

image-generation.generate

Generate an image from a text prompt with Muse Image.

The image is saved to account file storage. The response includes a signed URL for API users and download_code for agents to run vee3-get-file. When n is greater than 1, each returned image is stored separately.

Cost = 50 tokens per generated image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNoNumber of images to generate (1 to 10). Each returned image costs 50 tokens.
sizeNoOptional output size as WIDTHxHEIGHT (for example 1024x1536) or auto. This sets aspect ratio, not exact pixel size. Omit for the default aspect ratio.
promptYesText description of the image to generate or of the edit to apply.
file_nameNoOptional account-relative storage path for the image. When n is greater than 1, an index is inserted before the extension (for example art/fox.webp becomes art/fox-1.webp and art/fox-2.webp). If omitted, the file is stored under image-generation/ with a generated name.
output_formatNoEncoding of the returned image. webp is smaller; png is lossless.webp

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoEcho of the requested size when one was passed.
imagesNoGenerated images stored in account file storage.
promptNoEcho of the requested prompt.
statusNoAlways "completed" for a successful generation.
created_atNoISO 8601 timestamp.
token_costNoTokens charged for this request (50 times image_count).
image_countNoNumber of images returned and billed.
generation_idNoUnique identifier, prefix igen_.
output_formatNoEncoding of the stored images (webp, png, or jpeg).
install_commandNoOne-time command to install the Vee3 CLI (`npm install -g @vee3/cli`). On networks that inspect HTTPS, install may require Node 22.15+ with NODE_OPTIONS=--use-system-ca.
troubleshootingNoWhat to do if installation or downloading fails: re-read this tool's description via meta-tools.describe for setup and troubleshooting steps.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and covers important behavior: the image is saved to account file storage, the response returns a signed URL for API users and a download_code for agents, and n images are stored separately. It also discloses token cost, which is valuable operational context.

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?

Four sentences front-loaded with purpose, followed by storage/retrieval details, n behavior, and cost. It is economical and scannable; the cost statement is useful in the description but slightly redundant with the n parameter's schema description.

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?

The storage location, retrieval mechanism (vee3-get-file), multi-image separation, and cost are all covered, giving an agent enough operational context. Since an output schema exists, return-value details do not need to be spelled out in the description.

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%, and the schema already documents all parameters clearly (n range and cost, size format, file_name path behavior, output_format enum). The description adds no new parameter-specific meaning beyond the schema.

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?

'Generate an image from a text prompt with Muse Image' states a specific verb, resource, and underlying model. It is immediately distinct from the sibling image-generation.edit, and an agent can tell this is the creation path rather than the editing path.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description says nothing about when to choose generation over the sibling image-generation.edit, and it does not mention any exclusions or alternative tools. It focuses on mechanics such as storage and cost, leaving the agent to infer selection criteria from the tool name.

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

All Vee3 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

Resources