Skip to main content
Glama

WritersLogic business agents

print-estimate

Print resolution, bleed and uncompressed bitmap size arithmetic — Given an image's pixel size and a print size (inches, millimetres or centimetres) plus optional bleed, margin and target ppi, returns the effective ppi over trim plus bleed, whether it meets the target, the pixel count a target ppi needs, the largest print size a target ppi allows, the safe area, and the exact uncompressed bitmap size. Built for print-on-demand, layout and image-prep agents; the t

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": {
      "widthPx": "<widthPx>",
      "heightPx": "<heightPx>"
    },
    "name": "print-estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoUnit for print size, bleed and margin (default in).
bleedNoBleed added on each side of the trim, in unit (default 0).
marginNoSafe margin inside the trim on each side, in unit (default 0).
widthPxYesImage width in pixels.
channelsNoChannels per pixel for the raw size (default 3).
heightPxYesImage height in pixels.
targetPpiNoThe resolution you require, in pixels per inch.
printWidthNoTrim width in unit.
printHeightNoTrim height in unit.
ppiToleranceNoAccepted ppi difference for claimedEffectivePpi (default 0.5).
bitsPerChannelNoBits per channel (default 8).
claimedRawBytesNoAn uncompressed byte count you assert.
claimedEffectivePpiNoAn effective ppi you assert; checked against the computed value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does so well: it enumerates the return values (effective ppi over trim plus bleed, target pass/fail, required pixel count, max print size, safe area, exact uncompressed byte size). It stops short of saying whether claimed values are merely validated or error out, which matters for the assertion parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The output list is front-loaded and dense in a useful way, but the text ends mid-word ('the t'), leaving a dangling fragment that harms polish. One long run-on sentence also makes it harder to scan than a listed structure.

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 13-parameter, no-output-schema compute tool, the description does cover the principal return values, but truncation and silence on the claimed*/tolerance validation behavior leave an agent guessing about failure modes. Adequate but with clear gaps.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description restates the unit, bleed, margin, and target ppi semantics in prose but adds nothing about channels, bitsPerChannel, ppiTolerance, or the two claimed* validation parameters.

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 opening phrase 'Print resolution, bleed and uncompressed bitmap size arithmetic' states a specific verb (compute) and resource (print geometry), and the body enumerates concrete outputs. It is distinguishable from a generic box-sizing sibling like print-box, though it never names or contrasts with it explicitly.

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

Usage Guidelines2/5

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

The only guidance is an audience tag ('Built for print-on-demand, layout and image-prep agents'), which describes who, not when. There is no when-to-use, when-not-to-use, or comparison to the print-box sibling that plausibly overlaps.

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.

Resources