Skip to main content
Glama

image_fast

Generate images quickly using Flux Schnell for AI agents, balancing speed and cost at $0.002 per image with customizable dimensions.

Instructions

Generate an image quickly using Flux Schnell (faster, cheaper) ($0.002)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYes
widthNo
heightNo

Implementation Reference

  • index.js:18-18 (registration)
    Registration of the 'image_fast' tool within the TOOLS array.
    { name: 'image_fast', description: 'Generate an image quickly using Flux Schnell (faster, cheaper)', inputSchema: { type: 'object', properties: { prompt: { type: 'string' }, width: { type: 'number', default: 1024 }, height: { type: 'number', default: 1024 } }, required: ['prompt'] }, endpoint: '/image/fast', price: '$0.002' },
  • index.js:50-79 (handler)
    The 'callTool' function serves as the generic handler for all registered tools, including 'image_fast', by making HTTP requests to the IteraTools API.
    async function callTool(endpoint, params) {
      const fetch = (await import('node-fetch')).default;
      const isGet = ['GET'].includes((TOOLS.find(t => t.endpoint === endpoint) || {}).method);
      
      const url = isGet 
        ? `${BASE_URL}${endpoint}?${new URLSearchParams(params)}`
        : `${BASE_URL}${endpoint}`;
      
      const res = await fetch(url, {
        method: isGet ? 'GET' : 'POST',
        headers: {
          'Content-Type': 'application/json',
          'Authorization': `Bearer ${API_KEY}`,
        },
        body: isGet ? undefined : JSON.stringify(params),
      });
      
      const text = await res.text();
      let data;
      try { data = JSON.parse(text); } catch { data = { raw: text }; }
      
      if (!res.ok) {
        if (res.status === 402) {
          throw new Error(`Insufficient credits. Add credits at https://iteratools.com. Cost: ${TOOLS.find(t=>t.endpoint===endpoint)?.price || 'see docs'}`);
        }
        throw new Error(`API error ${res.status}: ${text.substring(0, 200)}`);
      }
      
      return data;
    }
Behavior3/5

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

No annotations provided, so description carries full burden. It successfully discloses cost ($0.002) and speed characteristics ('quickly', 'faster'), but omits return format (URL vs base64), rate limits, dimension constraints, or idempotency behavior.

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?

Single sentence with zero waste. Front-loads the action ('Generate'), specifies the model, and packs two key differentiators (speed, cost) into a compact form. Every clause earns its place.

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?

Adequate for basic tool selection but incomplete for invocation. Missing output schema coverage is expected, but the lack of parameter constraints (min/max dimensions, valid aspect ratios) for the dimension parameters leaves critical gaps given the 0% schema coverage.

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

Parameters2/5

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

Schema has 0% description coverage (no descriptions for prompt, width, height). Description fails to compensate—it doesn't mention parameters at all, leaving width/height constraints (valid ranges, step values) completely undocumented despite their defaults.

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?

Description states specific verb ('Generate') + resource ('image') + model ('Flux Schnell') and distinguishes from sibling 'image_generate' via explicit speed/cost positioning ('faster, cheaper'). The cost annotation ($0.002) further clarifies economic differentiation.

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?

Implies usage context through 'faster, cheaper' positioning, suggesting use when speed/cost matters over quality. However, it doesn't explicitly name 'image_generate' as the alternative for higher quality, requiring the agent to infer from the 'fast' suffix.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fredpsantos33/itera-tools-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server