Skip to main content
Glama

Perfect-bound cover spread

bpj_design_book_wrap
Read-onlyIdempotent

Estimate spine thickness and the spread of a softcover using leaf caliper, page count, and trim size before bleed.

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": {
      "width": "<width>",
      "height": "<height>",
      "pages": "<pages>",
      "caliper": "<caliper>"
    },
    "name": "bpj_design_book_wrap"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYes
widthYes
heightYes
caliperYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds the useful caveat that the estimate is pre-bleed, but says nothing about output units, rounding, or whether the spread includes wrap/allowance.

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?

A single front-loaded sentence with the verb, outputs, inputs, and the workflow caveat all present, and no filler wording.

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 no output schema, the description does name the two results an agent should expect (spine thickness, spread), which is the key thing it must supply. It stops short of stating output units or whether the spread figure is a single flat width, which would matter for downstream layout use.

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 description coverage is 0%, but the property titles carry units ('Trim width (mm)', 'Interior leaf caliper (mm)'), and the description names three of the four inputs, mapping trim size to width and height. The main residual ambiguity is whether 'pages' means leaves or sides and whether caliper is per leaf or per sheet, which materially affects spine math and is left unaddressed.

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 specific verb (estimate) and two concrete outputs (spine thickness and softcover spread) from named inputs, which separates it from geometry siblings such as bpj_design_saddle_folio or bpj_design_printable_size. It does not explicitly name an alternative, so differentiation is inferred from the domain vocabulary rather than stated.

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?

The phrase 'before bleed' situates the call in a prepress workflow, implying it is a pre-flight sizing step. There is no explicit statement of when to prefer a different tool, nor any prerequisite or exclusion, so guidance remains implied.

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.