Skip to main content
Glama

FreeDailyPro Book Publishing Tools

publishing_spine_width

Read-onlyIdempotent

Book spine and cover size calculator

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": {
      "trimWidthIn": "<trimWidthIn>",
      "trimHeightIn": "<trimHeightIn>",
      "pages": "<pages>",
      "thicknessIn": "<thicknessIn>"
    },
    "name": "publishing_spine_width"
  }
}

Input Schema

NameRequiredDescriptionDefault
dpiNoResolution used to give the cover size in pixels, a whole number from 72 to 1200. Default 300. null is treated as not sent.
pagesYesPage count, a whole number from 1 to 2000. Printed books have an even count; an odd number returns a warning.
bleedInNoBleed in inches added on every outer edge, 0 to 1. Default 0.125 for every platform. null is treated as not sent.
platformNoPrinter the result is labelled for: kdp (default), ingramspark or lulu. The formula is the same for all.
thicknessInYesPaper thickness in inches per page (one sheet is two pages), at least 0.0001 and at most 0.02, for example 0.002252 for KDP black and white on white paper. A value below 0.0001 is a 400.
trimWidthInYesTrim width of one page in inches, 2 to 14.
trimHeightInYesTrim height in inches, 2 to 14.
spineAllowanceInNoExtra width in inches added to (or, if negative, removed from) the spine, -0.5 to 0.5. Default 0. The final spine (pages x thicknessIn + spineAllowanceIn) must be above 0, otherwise the result is a 400. null is treated as not sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / platform / description
      Previous value: -"Printer the result is labelled for. Default kdp. The spine and cover formula (pages x thicknessIn + spineAllowanceIn; width = 2 x trim width + spine + 2 x bleed) is the same for every printer: platform only changes the label in summary and, for kdp, adds a warning when pages is outside 24 to 828 (black and white, white paper). It does not change bleed, spine or cover size. Use the thicknessIn and bleedIn your printer gives. null is treated as not sent."New value: +"Printer the result is labelled for: kdp (default), ingramspark or lulu. The formula is the same for all."
  2. Changed7 schema fields changed
    • changedInput schema / properties / bleedIn / description
      Previous value: -"Bleed in inches added on every outer edge, 0 to 1. Default 0.125."New value: +"Bleed in inches added on every outer edge, 0 to 1. Default 0.125 for every platform. null is treated as not sent."
    • changedInput schema / properties / dpi / description
      Previous value: -"Resolution used to give the cover size in pixels, a whole number from 72 to 1200. Default 300."New value: +"Resolution used to give the cover size in pixels, a whole number from 72 to 1200. Default 300. null is treated as not sent."
    • changedInput schema / properties / platform / description
      Previous value: -"Printer the numbers are for. Default kdp. For kdp a warning is returned when pages is outside 24 to 828 (black and white, white paper); the other printers have no built-in page limits."New value: +"Printer the result is labelled for. Default kdp. The spine and cover formula (pages x thicknessIn + spineAllowanceIn; width = 2 x trim width + spine + 2 x bleed) is the same for every printer: platform only changes the label in summary and, for kdp, adds a warning when pages is outside 24 to 828 (black and white, white paper). It does not change bleed, spine or cover size. Use the thicknessIn and bleedIn your printer gives. null is treated as not sent."
    • changedInput schema / properties / spineAllowanceIn / description
      Previous value: -"Extra width in inches added to (or, if negative, removed from) the spine, -0.5 to 0.5. Default 0."New value: +"Extra width in inches added to (or, if negative, removed from) the spine, -0.5 to 0.5. Default 0. The final spine (pages x thicknessIn + spineAllowanceIn) must be above 0, otherwise the result is a 400. null is treated as not sent."
    • changedInput schema / properties / thicknessIn / description
      Previous value: -"Paper thickness in inches per page (one sheet is two pages), above 0 and at most 0.02, for example 0.002252 for KDP black and white on white paper."New value: +"Paper thickness in inches per page (one sheet is two pages), at least 0.0001 and at most 0.02, for example 0.002252 for KDP black and white on white paper. A value below 0.0001 is a 400."
    • removedInput schema / properties / thicknessIn / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / thicknessIn / minimum
      Added value: +0.0001
  3. Changed23 schema fields changed
    • addedInput schema / properties / bleedIn / description
      Added value: +"Bleed in inches added on every outer edge, 0 to 1. Default 0.125."
    • addedInput schema / properties / bleedIn / maximum
      Added value: +1
    • addedInput schema / properties / bleedIn / minimum
      Added value: +0
    • addedInput schema / properties / dpi / description
      Added value: +"Resolution used to give the cover size in pixels, a whole number from 72 to 1200. Default 300."
    • addedInput schema / properties / dpi / maximum
      Added value: +1200
    • addedInput schema / properties / dpi / minimum
      Added value: +72
    • changedInput schema / properties / dpi / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / pages / description
      Added value: +"Page count, a whole number from 1 to 2000. Printed books have an even count; an odd number returns a warning."
    • addedInput schema / properties / pages / maximum
      Added value: +2000
    • addedInput schema / properties / pages / minimum
      Added value: +1
    • addedInput schema / properties / platform / description
      Added value: +"Printer the numbers are for. Default kdp. For kdp a warning is returned when pages is outside 24 to 828 (black and white, white paper); the other printers have no built-in page limits."
    • addedInput schema / properties / spineAllowanceIn / description
      Added value: +"Extra width in inches added to (or, if negative, removed from) the spine, -0.5 to 0.5. Default 0."
    • addedInput schema / properties / spineAllowanceIn / maximum
      Added value: +0.5
    • addedInput schema / properties / spineAllowanceIn / minimum
      Added value: +-0.5
    • changedInput schema / properties / thicknessIn / description
      Previous value: -"Paper thickness in inches per page, for example 0.002252 for KDP white paper"New value: +"Paper thickness in inches per page (one sheet is two pages), above 0 and at most 0.02, for example 0.002252 for KDP black and white on white paper."
    • addedInput schema / properties / thicknessIn / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / thicknessIn / maximum
      Added value: +0.02
    • addedInput schema / properties / trimHeightIn / description
      Added value: +"Trim height in inches, 2 to 14."
    • addedInput schema / properties / trimHeightIn / maximum
      Added value: +14
    • addedInput schema / properties / trimHeightIn / minimum
      Added value: +2
    • addedInput schema / properties / trimWidthIn / description
      Added value: +"Trim width of one page in inches, 2 to 14."
    • addedInput schema / properties / trimWidthIn / maximum
      Added value: +14
    • addedInput schema / properties / trimWidthIn / minimum
      Added value: +2
  4. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. Beyond that safety profile, the description adds no behavioral context such as what output is returned, how platform affects labeling, or what warnings/errors may occur.

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?

The description is a single front-loaded phrase with no wasted words. It is efficient, though its extreme brevity leaves little structural support for understanding the tool's output or scope.

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?

With no output schema, the description could reasonably say what dimensions or formats are returned and how platform labeling works. The rich input schema compensates for parameter gaps, but the description still omits return-value context for an eight-parameter calculator.

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 all eight parameters are already documented in the input schema. The description adds no additional parameter meaning, which is acceptable given the schema's completeness but does not exceed the baseline.

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?

The phrase "Book spine and cover size calculator" clearly identifies the resource (book spine/cover dimensions) and the operation (calculation). It is specific enough for an agent to know what the tool produces, though it does not distinguish itself from any sibling tools.

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

Usage Guidelines2/5

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

There is no guidance on when to use this calculator, when not to, or which publishing-related alternative might be appropriate. The description provides only a bare purpose statement without any usage context or prerequisites.

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