Skip to main content
Glama
Sign In

Designers

by com.allthepossibles
OverviewDiscussionsAdmin

Imposition planner

plan_imposition
Read-only

Plan imposition for a booklet or book. Pass pages (1 to 1024) and binding: saddle (stitched; one nested stack, pages in multiples of 4), perfect or sewn (gathered signatures of signature pages: 4, 8, 16, 32 or 64; 16 is the common offset size). Returns pages after padding to the next multiple, blank pages to add, number of signatures or sheets, and for saddle the printer-spread pairs for every sheet (outer and inner sides). With caliper_microns it estimates creep for saddle stitch: the sheet nested k sheets inside the outermost shifts its content outward by about k x caliper, so planned inward compensation for the outermost sheet is about (sheets - 1) x caliper. Printers use their own creep tables, and some compensate with 2 x caliper; treat this as an estimate.

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": {
      "pages": "<pages>"
    },
    "name": "plan_imposition"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYesPage count (total, including covers if self-cover)
bindingNoBinding
signatureNoPages per signature (perfect or sewn)
caliper_micronsNoThickness of one sheet in microns (for creep)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Although annotations already declare readOnlyHint=true and destructiveHint=false, the description adds important behavioral detail: what is returned (padded page count, blank pages, signature/sheet count, saddle spread pairs), how creep is estimated, and a caveat that printer tables vary. This is substantial context beyond the annotations.

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?

The description is one dense paragraph but front-loads the core action and then adds necessary detail. Every clause contributes to correct invocation: binding semantics, return values, or creep estimation caveats. There is no filler.

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, so the description must explain return values—and it does thoroughly. It covers all four parameters, the binding-specific behavior, and the estimation caveat, leaving nothing essential for correct invocation unstated.

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%, establishing a baseline of 3, but the description adds significant meaning beyond the schema: pages range 1–1024, how saddle vs perfect/sewn binding interpret the inputs, what signature values mean, and how caliper_microns drives the creep estimate. This materially improves correct parameter use.

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 uses a specific verb and resource: 'Plan imposition for a booklet or book.' It is clearly distinct from print-related siblings such as calc_print_spec or convert_paper_size, but it does not explicitly name or differentiate itself from any alternative tool.

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

Usage Guidelines4/5

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

The description gives clear contextual guidance for choosing binding modes and signature sizes, and explains when caliper_microns is useful. However, it does not state explicit exclusions or name alternative tools for related print-planning tasks.

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