Skip to main content
Glama
Sign In

Designers

by com.allthepossibles
OverviewDiscussionsAdmin

Print spec calculator

calc_print_spec
Read-only

Work out print document sizes. Pass trim_width and trim_height with unit (mm, cm, in, pt), optional bleed (default 3 mm; the common European figure, US printers often ask 0.125 in = 3.18 mm), safe margin inside trim (default 5 mm), and for books pages (counted as printed pages, 2 per leaf), caliper (thickness of ONE sheet of the paper) with caliper_unit (microns, mm, mil = thousandth of an inch, which paper trade calls points, or in), spine_extra_mm for glue allowance, and binding (perfect, saddle, none). Formulas: size with bleed = trim + 2 x bleed; safe area = trim - 2 x safe; spine = (pages / 2) x caliper + extra; cover spread width = 2 x trim width + spine + 2 x bleed. Spine is an estimate: the printer's own template and paper stock win, and hardcover case binding adds board thickness not computed here.

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": {
      "trim_width": "<trim_width>",
      "trim_height": "<trim_height>"
    },
    "name": "calc_print_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
safeNoSafe margin in the same unit (default 5 mm)
unitNoUnit
bleedNoBleed in the same unit (default 3 mm)
pagesNoPrinted page count (books)
bindingNoBinding
caliperNoThickness of one sheet
trim_widthYesFinished width
trim_heightYesFinished height
caliper_unitNoCaliper unit
spine_extra_mmNoExtra spine allowance in mm

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive/closed-world, and the description adds real behavioral context on top: parameters are defaults (3 mm bleed, 5 mm safe), the spine value is an estimate the printer's template may override, and hardcover case binding is explicitly out of scope. That is exactly the caveat an agent needs before trusting the result.

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?

It is a single dense paragraph but nearly every clause carries payload: defaults, unit equivalences, and the four formulas. It is front-loaded with purpose and formulas sit at the end where they belong; the only cost is that it reads as a wall of text rather than a list.

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?

With 10 parameters and no output schema, the description carries the return-value burden and largely meets it by giving the exact formulas for bleed size, safe area, spine, and cover spread. It stops short of naming the output fields or units of each returned value, which is the only remaining gap.

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

Parameters5/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, but the description meaningfully exceeds it: bleed is contextualised as European 3 mm vs US 0.125 in = 3.18 mm, caliper is specified as ONE sheet's thickness, mil is explained as thousandths of an inch which the paper trade calls points, and pages are counted as printed pages at 2 per leaf.

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 description opens with a specific verb and resource ('Work out print document sizes') and immediately enumerates the computed artifacts: bleed size, safe area, spine, cover spread. That clearly separates it from siblings like convert_paper_size or calc_print_resolution, though it never names an alternative.

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 implied rather than stated: 'for books' conditionally signals when the pages/caliper/binding parameters apply, and the defaults suggest typical use. There is no explicit when-not or pointer to related tools such as plan_imposition or convert_paper_size, so the agent must infer boundaries.

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

All Designers toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources