Skip to main content
Glama

generate_image

Creates an image from a text prompt through a web LLM and returns the saved file path under ./out/.

Instructions

Generate an image on the web LLM; returns the saved file path under ./out/.

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

Input Schema

NameRequiredDescriptionDefault
promptYes
timeoutNo
providerNogemini

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that a file is written to ./out/, but says nothing about whether the call blocks for the default 180s timeout, what happens on failure, or what permissions/session state are required.

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?

One short sentence with the action front-loaded and the output location appended; nothing is padded. The phrasing 'web LLM' is slightly awkward and the sentence could carry more without becoming long.

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

Completeness2/5

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

With no annotations and 0% schema coverage across three parameters, the description is too thin for a tool that writes files to disk and has a long default timeout. The existence of an output schema excuses it from explaining return shape, but not from covering provider/timeout semantics.

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 description coverage is 0% for all three parameters, so the description must compensate and does not. It never mentions prompt, timeout (default 180), or provider (default gemini) — 'web LLM' only faintly gestures at provider selection.

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 pairs a specific verb ('Generate') with a specific resource ('an image') and adds where the artifact lands ('saved file path under ./out/'). It is clear what the tool produces, though it never distinguishes itself from siblings like ask or list_providers.

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 statement of when to use this versus alternatives, no prerequisite such as requiring an authenticated session (despite a login sibling existing), and no guidance on choosing between providers. 'On the web LLM' is the only contextual hint and it is vague.

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