Skip to main content
Glama

Book cover size calculator

calculate_cover_size
Read-onlyIdempotent

Use this when an author asks how big their full wraparound paperback or hardcover cover file must be for KDP, IngramSpark or Lulu. Takes the trim size, interior page count, binding and paper; returns the total width and height including bleed and spine, the back/spine/front breakdown, the barcode area and a link to check it on pdfdocpreflight.com.

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": {
      "platform": "<platform>",
      "trim_size": "<trim_size>",
      "page_count": "<page_count>"
    },
    "name": "calculate_cover_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
paperNoInterior paper and ink. KDP: 'bw-white' (Black ink, white paper), 'bw-cream' (Black ink, cream paper), 'bw-groundwood' (Black ink, groundwood paper), 'standard-color' (Standard color ink, white paper), 'premium-color' (Premium color ink, white paper). IngramSpark: 'groundwood-38-bw' (38# Groundwood, B&W), 'groundwood-40-bw-uk' (40# Groundwood, B&W (UK)), 'creme-50-bw' (50# Crème, B&W), 'white-50' (50# White, B&W or Color), 'white-70' (70# White, B&W / Color / Premium / Ultra Premium Color). Lulu: leave out (its spine width does not depend on paper). If you leave it out for KDP or IngramSpark, the result lists every paper so you can compare.
bindingNoBinding. 'paperback' (default). KDP hardcover: 'hardcover' (KDP only offers case laminate). Lulu and IngramSpark: 'hardcover-casewrap' (printed case) or 'hardcover-jacket' (cloth case with dust jacket).paperback
platformYesPrint platform: 'kdp' (Amazon KDP), 'ingramspark' or 'lulu'.
trim_sizeYesFinished book size, width × height, e.g. '6x9', '5.5 x 8.5 in', '152 x 229 mm', or a trim id from get_platform_specs (e.g. Lulu 'us-trade'). Width first.
page_countYesInterior page count: every page of the interior PDF, including blank and front-matter pages (not sheets or leaves).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the bar is lower, but the description still adds real value by disclosing the return contents: total width/height with bleed and spine, back/spine/front breakdown, barcode area, and a preflight link. With no output schema, this is the only place that output shape is described, though it omits any note about platform-specific constraints or failure cases.

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 sentences, with the when-to-use trigger front-loaded and the return payload second. No filler, no repetition of the title or annotation data.

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 five-parameter calculator with no output schema, the description covers both the intended invocation context and the return shape, which is what an agent needs. It falls just short of complete by not mentioning platform-specific edge cases (e.g. hardcover page-count minimums) that could make a call fail.

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 100% and the parameter documentation is unusually rich (paper enums per platform, page_count definition including blanks, trim_size format examples). The description only lists the inputs ('trim size, interior page count, binding and paper') without adding meaning beyond the schema, so the baseline of 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 description gives a specific verb and resource ('how big their full wraparound ... cover file must be') scoped by three named platforms, which cleanly separates it from the sibling calculate_spine_width (spine only) and get_platform_specs (specs lookup). An agent can select it without opening the schema.

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 triggering situation clearly ('when an author asks how big their ... cover file must be') and enumerates the platforms covered. It does not explicitly exclude or route to calculate_spine_width for spine-only questions, so the alternative-selection guidance is implicit rather than spelled out.

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