Skip to main content
Glama

Calculate cover dimensions

calculate_cover_dimensions
Read-onlyIdempotent

Calculates exact cover size, including spine and bleed, for a Lulu print product and page count. Use it to size cover files correctly before printing.

Instructions

Get the exact cover size (including spine and bleed) needed for a product and page count.

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": {
      "pod_package_id": "<pod_package_id>",
      "interior_page_count": "<interior_page_count>"
    },
    "name": "calculate_cover_dimensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoUnit for the result. Lulu's default is pt.
pod_package_idYesLulu product SKU (pod_package_id): trim size, ink, quality, binding, paper and finish. Dotted format, e.g. '0600X0900.BW.STD.PB.060UW444.MXX' (6x9in black-and-white standard paperback, matte). Lulu still accepts the older 27-character format without dots until 1 February 2027. Build one with Lulu's pricing calculator: https://developers.lulu.com/price-calculator
interior_page_countYesNumber of interior pages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds that the result accounts for spine and bleed, which is genuine context, but says nothing about precision, rounding, or what the response object looks like despite there being no output schema.

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?

One front-loaded sentence with no filler; the returned components and required inputs are packed into a single readable clause.

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?

For a pure calculation tool with no output schema, the description tells you conceptually what comes back (a size with spine and bleed) but not the structure — no field names, dimensionality, or units of the response. Combined with absent when-to-use guidance, it is adequate but leaves real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes slightly beyond by framing pod_package_id as 'product' and interior_page_count as 'page count', clarifying that the two required inputs are the size determinants. It does not add format or validation detail beyond the schema.

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?

States a concrete verb ('Get') and resource ('exact cover size'), and enumerates the returned components (spine, bleed) plus the inputs (product, page count). It is clearly distinct from validation siblings like get_cover_validation, though it never names them explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the pre-flight sizing step before creating a cover, but there is no statement of when to prefer it over validate_cover_file or get_cover_validation, and no prerequisites are given.

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