Skip to main content
Glama

Book Cover Maker - Abracadabrax

Prepare Book Cover

prepare_book_cover

Prepare a front cover with Abracadabrax for an ebook, a Kindle book or a print book in 2:3 portrait format, from the title, the subtitle, the author name, the genre and the visual style, with the text set in the cover design. Returns the settings and the credits required; nothing is generated and no credits are spent. No sign-in is needed to prepare. Original designs only: do not use it for copyrighted characters, existing franchises, brand logos, trademarks or real celebrities; offer the user an original alternative instead. Text only: do not use it for uploaded, attached or reference images or videos (editing, background removal, upscaling, image-to-video); for those, point the user to the Abracadabrax workspace.

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

Input Schema

NameRequiredDescriptionDefault
genreNoGenre, e.g. thriller, romance, fantasy, self-help, business, children's picture book.
titleYesBook title, spelled exactly.
authorNoAuthor name as printed on the cover.
model_idNoOptional image model id: nano-banana-pro (default, sharp text), nano-banana-2, flux-2-pro.
subtitleNoOptional subtitle or series name.
visual_styleNoCover image and style, e.g. a lone lighthouse in a storm, moody photo; or bold typographic minimal.

Output Schema

NameRequiredDescriptionDefault
jobNo
stateYes
balanceNo
messageYes
projectYes
dashboard_urlYes
credits_requiredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Adds real context beyond annotations: no generation, no credits spent, no sign-in required, returns the settings and credits needed, and originality/text-only content policies. The only soft spot is a mild tension with readOnlyHint=false — it is unclear whether the 'prepared' settings persist as state — but this is not a contradiction.

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?

Purpose and output behavior are front-loaded, followed by the two exclusion rules, with zero filler sentences. Every clause either defines the operation or prevents a misuse, which is exactly what an agent needs before calling.

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

Completeness5/5

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

With an output schema present, return values need not be described, yet the description still covers cost, auth, and side-effect expectations. Combined with the fully documented schema and the content-policy exclusions, an agent has everything needed to call this correctly.

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 all six parameters with examples and limits. The description enumerates the same inputs (title, subtitle, author, genre, visual style) but omits model_id and adds no format or syntax detail, so baseline 3 applies.

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?

States a specific verb (prepare) and resource (front cover via Abracadabrax) plus format (2:3 portrait), supported inputs, and the fact that text is set into the design. It also explicitly separates itself from generate_media by stating 'nothing is generated', so an agent can route correctly without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use (ebook/Kindle/print covers from title, subtitle, author, genre, style) and two clear when-not-to-use cases: copyrighted characters, franchises, logos, trademarks or real celebrities (offer an original alternative), and uploaded/attached/reference images or videos (point to the Abracadabrax workspace). Alternatives are named, not implied.

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