Skip to main content
Glama
Sign In

Book Cover Generator

by io.github.otsirh
OverviewDiscussionsAdmin

Create a mockup of a cover

create_mockup
Read-only

Draw a cover as a product shot (a 3D book, flat, on an e-reader) or on a social card with a line of text. Answers with the picture and its links.

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": {
      "title": "<title>"
    },
    "name": "create_mockup"
  }
}

Input Schema

NameRequiredDescriptionDefault
svgNoAlso answer with the SVG markup (large).
caseNoThe title in capitals, or as typed.
fontNoThe title's font instead of the style's: serif, didone, garamond, sans, geometric, humanist, condensed, display, mono.
kindNoDefault: book.
langNoThe text's language, a tag such as tr or zh-Hant, for its capitals (Turkish İ) and letterforms. Default: from the text.
seedNoEvery random choice comes from it: the same seed draws the same cover; another, a variation.
textNoThe line on a card, square or story, such as "Out now".
badgeNoA seal in a corner, such as "Winner of the Hugo Award".
genreNoWith no style, pick one that suits a genre: literary (Literary), thriller (Thriller & crime), horror (Horror), romance (Romance), fantasy (Fantasy & sci-fi), children (Children’s), nonfiction (Non-fiction).
styleNoA style, by id or name (see list_styles), or "random" (the default: the seed picks one).
titleYesThe book's title. A line break (\n) breaks its line on the cover.
authorNoThe author's name.
colorsNoYour own colours instead of a palette, as hex.
creditNoA credit under the subtitle, such as "Translated by Ann Lee".
formatNopaperback, ebook, square, or a size in px such as 1600x2560 (Kindle). Default: paperback (2:3).
seriesNoA series line above the title, such as "Book Two of the Ember Cycle".
paletteNoA palette, by id or name (see list_palettes), or "auto" (the default: the seed picks one).
textureNoA fine film grain.
subtitleNoA subtitle or tagline.
variantsNoChoices a style lets you pin, as list_styles shows them, such as { "scene": "forest" }.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With readOnlyHint=true and openWorldHint=false already declaring the safety profile, the description adds genuinely new information by stating the response contains the picture and its links – important because there is no output schema. It does not cover determinism or how long generation takes, but the response-payload disclosure is the key behavioral fact an agent needs.

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?

Two tight sentences with zero filler, front-loading the core action and following with the return value. 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?

For a 20-parameter tool with nested objects and no output schema, the description covers purpose and return payload but omits routing guidance against create_cover and says nothing about the extensive customization surface (style, palette, variants) that the schema exposes. Adequate given full schema coverage, but not complete for the tool's complexity.

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% across all 20 parameters, including seed determinism, kind default, and style/palette lookup references, so the schema carries the semantic load. The description only lightly maps 'product shot' and 'social card' onto the kind enum, adding marginal meaning beyond the structured fields – baseline 3 applies.

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?

States a concrete verb and resource ('Draw a cover as a product shot') and enumerates the output shapes (3D book, flat, e-reader, social card with a line of text). That gives an agent a clear picture of what it produces, though it never names the sibling create_cover or explains how the two differ.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The mention of product shots and social cards implies the use case, but there is no explicit when-to-use/when-not guidance and no reference to the sibling create_cover. An agent must infer the choice between mockup generation and plain cover creation from the name alone.

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

All Book Cover Generator 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