Skip to main content
Glama
hedging8563

TokenLab MCP Server

by hedging8563
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Create image

create_image_file

Generate image files from text prompts or reference images for text-to-image, image-to-image, and image-edit tasks. Set model, size, format, and output options to produce saved image results.

Instructions

Creates an image given a prompt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNo
seedNo
sizeNo
userNo
asyncNo
imageNoLocal reference image upload for compatible image-to-image models. Pass local file path.
modelYesModel to use. Send this explicitly.
styleNo
promptYesImage description
qualityNo
mask_urlNo
operationNo
backgroundNo
image_urlsNoComma-separated reference image URLs.
moderationNo
resolutionNo
compressionNo
aspect_ratioNo
expand_promptNo
output_formatNo
prompt_extendNoFor z-image-turbo, enable prompt expansion. Defaults to false. Enabling it uses the model's prompt-…
negative_promptNo
response_formatNo
output_compressionNo
reference_image_urlsNoComma-separated reference image URLs for compatible model families.
X-TokenLab-Delivery-PolicyNoPer-request Delivery policy. Overrides the API key and Workspace defaults. Auto tries TokenLab Veri…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.26
    • addedInput schema / properties / prompt_extend
      Added value: +{
+  "description": "For z-image-turbo, enable prompt expansion. Defaults to false. Enabling it uses the model's prompt-…",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv0.6.24
    • addedInput schema / properties / X-TokenLab-Delivery-Policy
      Added value: +{
+  "description": "Per-request Delivery policy. Overrides the API key and Workspace defaults. Auto tries TokenLab Veri…",
+  "enum": [
+    "auto",
+    "verified",
+    "official"
+  ],
+  "type": "string"
+}
  3. Changed4 schema fields changedv0.6.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / seed / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / seed / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / stream
      Removed value: -{
-  "const": false,
-  "description": "Image streaming is not exposed through MCP tool calls; omit stream or set it to false.",
-  "type": "boolean"
-}
  4. Addedv0.3.1

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: no mention of cost/billing for generations, latency, async behavior (the 'async' param hints at long-running jobs), rate limits, or moderation rejection handling. With annotations present the bar is lower, but zero added context merits a 2.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, which is structurally clean. However, the brevity here reflects under-specification rather than disciplined conciseness, so it earns only a middling score.

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

Completeness1/5

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

For a 26-parameter generative tool spanning three distinct operations, with no output schema and no annotation detail about returns, one sentence is wholly inadequate. Nothing tells the agent how the returned image is delivered (url vs b64_json), how async jobs are polled via get_task_status, or how reference images are supplied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

26 parameters with only 27% schema description coverage, and the description explains none of them. Critical unlabeled parameters include operation (text-to-image / image-to-image / image-edit), n, seed, size, aspect_ratio, resolution, quality, style, mask_url, background, response_format, and async. An agent cannot infer correct usage from a single sentence when three-quarters of the parameters carry no documentation anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Creates an image given a prompt' is essentially the title restated (title: 'Create image') with the trivial addition of the prompt input. It never explains what the '_file' variant is or how it differs from the sibling tools create_image, edit_image, or edit_image_file, which is the one thing an agent most needs. A near-tautology of the name.

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?

There is no when-to-use guidance, no mention of prerequisites, and no routing to alternatives. With siblings named create_image and edit_image_file present, an agent has no basis from the description for choosing this tool. Nothing is misleading, but nothing is offered either.

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