Skip to main content
Glama

Printable image dimensions

bpj_design_printable_size
Read-onlyIdempotent

Find physical print dimensions from raster size at a target pixel density without resampling.

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": {
      "pixelsWide": "<pixelsWide>",
      "pixelsHigh": "<pixelsHigh>",
      "ppi": "<ppi>"
    },
    "name": "bpj_design_printable_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
ppiYes
pixelsHighYes
pixelsWideYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safe, deterministic, non-mutating profile is covered structurally. The description adds 'without resampling', which usefully clarifies that no image data is altered, but it does not state the output unit (presumably inches, given px/in input) or precision.

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?

A single front-loaded sentence with no filler; the operative concept (physical print dimensions) leads and the constraint (no resampling) follows. Nothing is redundant, though one more clause on output units would still have been cheap.

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?

This is a small, closed-form calculation with three required parameters and no output schema, so the description need not explain return structure. However, it leaves the output unit unstated, which for a unit-conversion tool is the one piece of information an agent most needs to report results correctly.

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 0%, so the description carries the burden. It does map the three inputs conceptually ('raster size' for pixelsWide/pixelsHigh and 'target pixel density' for ppi), and the schema titles supply the units (px, px/in), but the description adds no format, range, or interpretation guidance of its own.

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 gives a specific verb and resource ('Find physical print dimensions') plus the two input quantities (raster size, pixel density), which is enough to distinguish this from inverse or resampling utilities such as bpj_design_effective_ppi. It stops short of naming any sibling, so differentiation is inferential rather than explicit.

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 only implied: the phrase 'at a target pixel density without resampling' signals this is a pure conversion for planning a print size, but there is no statement of when to prefer it over alternatives or any precondition. An agent must infer the context from the name and purpose.

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.