Skip to main content
Glama
Venice MCP Server

Venice MCP Server

Official
by veniceai

Venice Image Generate

venice_image_generate

Generate images from text prompts across multiple models, with controls for size, seed, style references and NSFW output where the model allows.

Instructions

Generate an image. Supports Flux 2 Pro/Max, Lustify SDXL, Anime (WAI), Qwen Image, GPT Image, Nano Banana Pro and others. Uncensored: NSFW prompts allowed where the model permits. Supports x402 wallet auth (no Venice account needed) and API key.

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

Input Schema

NameRequiredDescriptionDefault
seedNo
modelNoDefaults to flux-2-pro.
stepsNo
widthNo
formatNo
heightNo
promptYes
qualityNoModel-specific quality tier; may change pricing.
variantsNoNumber of images. Only supported with non-binary responses.
safe_modeNo
resolutionNoModel-specific resolution tier such as "1K", "2K", or "4K"; the API validates supported values.
aspect_ratioNoModel-specific aspect ratio such as "1:1" or "16:9"; the API validates supported values.
style_presetNoSee venice://styles.
enhance_promptNoRewrite the prompt before generation. Adds up to ~30 seconds and a charge when applied.
negative_promptNo
style_referencesNoModel-specific style references. Check the model maxStyleReferences capability.
enable_web_searchNoAllow supported models to use web search; additional credits may apply.
disable_prompt_optimization_thinkingNoSkip prompt-optimization thinking on supported models.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.3.0
    • addedInput schema / properties / aspect_ratio
      Added value: +{
      +  "description": "Model-specific aspect ratio such as \"1:1\" or \"16:9\"; the API validates supported values.",
      +  "type": "string"
      +}
    • addedInput schema / properties / disable_prompt_optimization_thinking
      Added value: +{
      +  "description": "Skip prompt-optimization thinking on supported models.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / enable_web_search
      Added value: +{
      +  "description": "Allow supported models to use web search; additional credits may apply.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / enhance_prompt
      Added value: +{
      +  "description": "Rewrite the prompt before generation. Adds up to ~30 seconds and a charge when applied.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / format
      Added value: +{
      +  "enum": [
      +    "jpeg",
      +    "png",
      +    "webp"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / quality
      Added value: +{
      +  "description": "Model-specific quality tier; may change pricing.",
      +  "enum": [
      +    "low",
      +    "medium",
      +    "high"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / resolution
      Added value: +{
      +  "description": "Model-specific resolution tier such as \"1K\", \"2K\", or \"4K\"; the API validates supported values.",
      +  "type": "string"
      +}
    • addedInput schema / properties / style_references
      Added value: +{
      +  "description": "Model-specific style references. Check the model maxStyleReferences capability.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "image": {
      +        "description": "Style image URL, data URI, or raw base64 (under 8MB).",
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "strength": {
      +        "maximum": 1,
      +        "minimum": 0.1,
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "image"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / variants
      Added value: +{
      +  "description": "Number of images. Only supported with non-binary responses.",
      +  "maximum": 4,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true and non-idempotent, non-destructive writes, but the description adds genuinely non-structured context: content policy for NSFW prompts and two distinct authentication paths (x402 wallet vs. API key). What it omits is cost/credit impact and the difference between binary and non-binary responses, which is the gate for `variants`.

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?

It leads with the core action in three words and follows with the two facts an agent most needs (model coverage, auth options). The model enumeration is somewhat bulky but each named family earns its place by hinting at available `model` values.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 18-parameter generative tool with no output schema, the description should say what comes back (image URL vs. base64 binary, since `variants` only works with non-binary responses) and give a default size/format hint. Auth and content policy are covered, but the return shape and cost implications remain unstated.

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?

The description's model list maps loosely onto the `model` parameter (which defaults to flux-2-pro per the schema) but does not enumerate valid string values or explain the interaction between `model` and the model-specific `resolution`, `aspect_ratio`, `quality`, and `style_references` options. At 56% schema coverage across 18 parameters, the description adds only marginal meaning beyond the schema, so a 3 is appropriate.

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?

"Generate an image" is a specific verb+resource and the named model families (Flux 2 Pro/Max, Lustify SDXL, Qwen Image, GPT Image) make clear this is text-to-image synthesis rather than editing or upscaling. It stops short of explicitly naming siblings like venice_image_edit or venice_image_upscale, so the differentiation is inferred rather than stated.

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?

It gives useful context (NSFW prompts allowed where the model permits, x402 wallet auth means no Venice account is required, or use an API key), which tells an agent about access prerequisites. However, there is no explicit when-to-use vs. when-not guidance and no pointer to venice_image_edit for modifying an existing image, so the routing is left implied.

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