Skip to main content
Glama
Sign In

Epublys

by com.epublys
OverviewDiscussionsAdmin

generate_cover

Generate an AI book cover image using FLUX. Describe your vision, pick a genre, and get a portrait JPEG cover — 768×1152 when the model honours the requested size, otherwise its default square. The AI enhances your prompt with professional composition guidance while preserving your creative vision.

Pro only ($9/mo). Upgrade at https://epublys.com/pricing

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_cover"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoRandom seed for reproducible generation
genreNoBook genre — affects style and composition
titleNoBook title — used to synthesize a cover concept when no description is given (not rendered on cover)
authorNoAuthor name (for context, not rendered on cover)
descriptionNoCreative description of the desired book cover (max 2000 chars). Either description or title is required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations at all, the description carries the full behavioral burden and does meaningful work: it discloses output format (JPEG, portrait), exact dimensions with the caveat that the model may fall back to its default square, prompt-augmentation behavior, and a subscription gate with pricing. Gaps remain on failure modes, generation latency, and what happens when neither title nor description is supplied.

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?

Two short paragraphs, front-loaded with the core action and output shape, with the paywall constraint in a clearly separated line. The pricing URL sentence is mildly promotional but carries actionable routing information; little else 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 5-parameter tool with no output schema and no annotations, the description supplies the essential missing context: return format, image dimensions, model-dependent size variance, and the paid-tier requirement. An agent knows enough to call it, though ambiguity around the empty-arguments case is unresolved.

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 every parameter is already documented in the schema, and the description only loosely maps to them ('Describe your vision, pick a genre'). It adds no syntax or format detail for seed, author, or the title/description fallback rule beyond what the schema states, so the 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?

The first sentence names a specific verb and resource — 'Generate an AI book cover image using FLUX' — plus the underlying model, which no sibling tool (all EPUB conversion/metadata utilities) covers. The scope is narrow enough that an agent can distinguish it from every listed sibling at a glance.

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 states the interaction pattern ('Describe your vision, pick a genre') and surfaces a hard prerequisite: Pro-only at $9/mo, with a pointer to the upgrade path (the upgrade_to_pro sibling). It does not name explicit when-not-to-use cases, but there is no competing cover-generation tool to route away from.

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

All Epublys 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