Skip to main content
Glama
Sign In

1gateway

by io.github.code0xff
OverviewDiscussionsAdmin

Safe text-to-image: FLUX.1 schnell 1024x1024 JPEG with prompt and output safety checks

ai_image

Use when an agent needs an image from a text prompt. Input: prompt (max 1000 chars), optional steps (1-8, default 4). Output: JSON with a 1024x1024 JPEG (base64), steps, model, safety verdicts. Prompt screened by blocklist + Llama Guard 3, image by a vision check; sexual, minor, deepfake or gore requests refused 422, not charged. Not stored. Example: ?prompt=isometric%20illustration%20of%20a%20tiny%20robot%20cafe Price: $0.02 USDC (Base or Solana) via x402.

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

Input Schema

NameRequiredDescriptionDefault
stepsNoDiffusion steps (default 4; more = finer detail, slower)
promptYesWhat to draw (English works best). Sexual content, minors in suggestive scenes, real-person deepfakes and gore are refused (422, not charged)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly: it discloses safety screening (blocklist + Llama Guard 3 and vision check), refusal behavior (422, not charged), data retention (not stored), and pricing ($0.02 USDC via x402). This gives the agent a complete picture of side effects and constraints.

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?

The description is a single dense paragraph that is front-loaded with the use case, then input/output details, safety, example, and price. Every sentence contributes relevant information, though the example query string and payment details make it slightly cluttered.

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

Completeness5/5

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

Given there are no annotations and no output schema, the description fully covers the necessary context: purpose, input constraints, output format, safety behavior, retention, and pricing. An agent can call the tool correctly without needing additional structured fields.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by specifying the prompt max length (1000 chars) and the steps range (1–8, default 4), which are not present in the schema. These details help the agent construct valid inputs.

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?

The description clearly states the tool generates an image from a text prompt, specifies output format (1024x1024 JPEG), and implies the verb 'generate' through context. However, it does not explicitly differentiate this tool from sibling image-related tools like satellite_image or render_png, leaving the agent to infer that this is the only text-to-image generator.

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 opening sentence 'Use when an agent needs an image from a text prompt' provides a clear condition for use. There is no guidance on when to avoid this tool or which alternatives to use for other image needs, but the context is sufficiently clear for a generation tool.

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

All 1gateway toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources