Skip to main content
Glama

Spine width calculator

calculate_spine_width
Read-onlyIdempotent

Use this when an author asks for a book's spine width for KDP, IngramSpark or Lulu, or whether their book is thick enough for spine text. Takes the interior page count, binding and paper; returns the width in inches and mm, the formula used, the spine-text rule and a link to check it on pdfdocpreflight.com. For the full cover size, use calculate_cover_size instead.

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>",
      "page_count": "<page_count>"
    },
    "name": "calculate_spine_width"
  }
}

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'.
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.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real context beyond that: the response includes inches, mm, the formula used, the spine-text rule, and an external verification link, and the schema notes the fallback behavior of listing every paper when paper is omitted. It does not discuss error handling (e.g. page counts outside platform limits), which keeps it from a 5.

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, front-loaded with the trigger condition, then the return summary, then the alternative tool. No filler and nothing buried.

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?

There is no output schema, but the description enumerates what comes back (width in inches and mm, formula, spine-text rule, verification link), which is exactly what an agent needs to chain the result. Combined with fully documented parameters and safety annotations, nothing material is missing.

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% and carries detailed per-platform enum meanings, so the schema does the heavy lifting. The description restates the inputs at a high level ('interior page count, binding and paper') and notably omits the required platform parameter, adding no meaning the schema doesn't already provide.

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 and resource (compute a book's spine width) and names the platforms it covers (KDP, IngramSpark, Lulu) plus the secondary question it answers (is the book thick enough for spine text). It explicitly distinguishes itself from the sibling calculate_cover_size, so an agent can route 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?

The trigger is spelled out as a concrete author request, and the exclusion is explicit: for the full cover size, use calculate_cover_size instead. The spine-text-thickness use case is also named, so both common intents are covered.

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