Skip to main content
Glama

Generate images

generate

options lists models, age ranges, and layouts. quote returns the price, matchNote, and locked without spending. The plan branch of the schema is the field list; title and locale belong on books create. Pass locked and confirmToken to books create. Omit imageModelId to use account defaultImageModelId. Show the summary and wait for the user to accept it. start spends tokens and requires the matching confirmToken. A pageId start uses the quoted age, layout, and model. Book-wide settings belong on books update. status with bookId returns pages[].status and ready. On 402, tell the user to open /pricing. Image generation spends the website token balance. Purchases happen at /pricing; this tool never takes payment.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare non-read-only, non-destructive, non-open-world, so the description carries most of the behavioral load and does so well: quote costs nothing, start spends tokens and needs a matching confirmToken, a pageId start inherits the quoted age/layout/model, 402 means send the user to /pricing, and payment never happens here. It omits what start returns (e.g. a jobId) and any concurrency or rate-limit behavior.

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?

Individual sentences are dense and nearly waste-free, but the ordering is chaotic — it opens with return values of options/quote, jumps to the plan branch, then to books create, then back to start, then to 402 and payments. Nothing is front-loaded, and the fragmentary style makes the seven-op structure hard to hold in mind.

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 seven-branch tool with no output schema, the description covers the costly parts an agent must get right: the quote→confirm→start flow, token spend, the 402 escape hatch, and which fields belong on sibling tools. Remaining gaps are the return shape of start (job identifier) and how status polling should be sequenced after a start.

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 description coverage is 100%, so the schema already documents confirmToken, imageModelId defaults, layout/pageLayout aliasing, and confirmToken composition; most description statements merely restate this. The genuine additions are scope notes about which fields belong on which sibling tool (books create vs books update), which is routing rather than parameter meaning, so the baseline 3 applies.

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

Purpose3/5

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

The description never front-loads a statement of what the tool does; the closest is the trailing 'Image generation spends the website token balance.' The op vocabulary (options, quote, start, status) and the quote-then-confirm workflow have to be reconstructed from scattered fragments, though 'start spends tokens and requires the matching confirmToken' does convey the core action.

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?

Gives real routing rules: use options to list models/ages/layouts, quote to price without spending, start to actually spend, and 'Show the summary and wait for the user to accept it.' It also names ownership boundaries with siblings ('title and locale belong on books create', 'Book-wide settings belong on books update') and prescribes the 402 path to /pricing. It stops short of explicit when-not-to-use exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources