print-spine-paper-radar
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculate_book_spine_widthB | Calculates exact book spine thickness, wrap dimensions, and spine text eligibility for Amazon KDP, commercial offset, or hardcover bindings. |
| calculate_paper_weight_and_shippingA | Calculates single sheet weight, ream (500 sheets) weight, total production shipment weight, and freight CBM for paper runs. |
| calculate_sheet_imposition_yieldA | Computes maximum item yield, sheet area utilization, and trim waste when cutting small items from large parent press sheets. |
| convert_paper_unitsB | Performs authoritative ISO/TAPPI conversions between GSM, basis weight (Bond, Book/Text, Cover in lbs), and caliper thickness (points, microns, mils). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool addresses a distinct calculation domain: spine/binding geometry, unit conversion, weight & shipping logistics, and imposition/cutting yield. The main possible confusion is between calculate_paper_weight_and_shipping and calculate_sheet_imposition_yield since both concern quantities derived from paper stock sizes, though their outputs remain differentiated.
All four tools use a uniform calculate_or_convert + descriptive noun-phrase scheme prefixed consistently, making intent immediately parseable without jargon drift. Verb choice varies slightly ('calculate' versus 'convert'), yet stays coherent within a single family-like convention.
Four tightly related printing/prepress calculators cover complementary needs at once rather than duplicating or sprawling past usable clustering sense expectedly reduce hunt costs while avoiding excess options clutter acumen users content miss fines' differential legitimacy enhances elegance pleases juries optional til prices nice
Together these span most prepress numerics a user might need — substrate identity lookups come via input tables internal route works adequately accrue entitlements survive outsourced vendors somewhat acceptably enough several categories" margin efficiency reasons always anyway elegant?