Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Generate Image

generateImage
Destructive

Generate one image from a text prompt and save it as a one-file upload, ready to include in a Cloady site via createUpload.

Instructions

Draws one picture from a prompt and keeps it as a one-file upload. Ship it with a site by putting { path, fromUpload: uploadId } in createUpload; an upload that no app uses within three hours is deleted. At most 40 an hour per account.

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": {
      "workspaceSlug": "<workspaceSlug>"
    },
    "name": "generateImage"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestBodyNoThe JSON request body.
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare openWorldHint=true and destructiveHint=true. The description adds useful behavior: generation consumes a rate limit, the artifact is a single-file upload with a 3-hour retention rule tied to app usage, and the tool does not return a URL — the agent must feed the uploadId into createUpload. It doesn't cover cost or failure modes.

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?

Three tight sentences lead with the core action, then the integration path, then the constraints. The phrasing 'putting { path, fromUpload: uploadId } in createUpload' is slightly compressed, but no sentence is wasted.

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

Completeness4/5

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

For a generative, destructive-capable write tool with no output schema, the description covers the artifact lifecycle, the deletion window, and the throughput limit. It still does not say what the response contains, such as where uploadId appears, which an agent needs to complete the createUpload handoff.

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?

Schema coverage is 50%: prompt and shape are documented in the schema, and the description only echoes 'from a prompt'. The workspaceSlug parameter is left unexplained in both places, so the description does not make up for the schema gaps.

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?

The first sentence names a concrete verb and resource: 'Draws one picture from a prompt and keeps it as a one-file upload,' and it states what the tool produces (an upload artifact). This clearly separates it from siblings such as lookupImage and createUpload, which do different things.

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?

It explains the follow-up step in plain terms: pass { path, fromUpload: uploadId } to createUpload to ship the image with a site, and it states the 40/hour limit. It does not say when to avoid this tool or point to an alternative such as lookupImage for already-generated images, so it falls short of full routing guidance.

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