Skip to main content
Glama

Trim and bleed canvas

bpj_design_bleed_canvas
Read-onlyIdempotent

Build delivery canvas dimensions and trim offsets from a uniform bleed allowance.

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>",
      "bleed": "<bleed>"
    },
    "name": "bpj_design_bleed_canvas"
  }
}

Input Schema

NameRequiredDescriptionDefault
bleedYes
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety profile is covered. The description adds that the result is derived purely from inputs ('Build ... from a uniform bleed allowance'), reinforcing a deterministic computation, but it says nothing about output units, whether offsets are returned per edge, or rounding behavior.

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 tight sentence with the output front-loaded and no wasted clauses. Slightly abstract wording ('Build delivery canvas dimensions') costs a little immediate readability but nothing is redundant.

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 three-required-parameter pure calculator with no output schema, the description should say what the return looks like (canvas width/height plus per-edge offsets). It gestures at the outputs but does not define them, leaving an agent to guess the result shape.

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 reported as 0%, so the description must carry meaning and it does partially: 'trim' qualifies width/height and 'uniform bleed allowance' clarifies that bleed applies equally on every edge. It does not state units (mm) or that bleed must be non-negative, both of which are only visible in the schema titles and bounds.

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 names a specific action (build) and specific outputs (delivery canvas dimensions and trim offsets) plus the input basis (a uniform bleed allowance), so an agent can tell this is a print-geometry calculator. It does not differentiate itself from geometry siblings such as bpj_design_printable_size or bpj_design_sheet_imposition, which keeps it below 5.

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?

There is no when-to-use statement, no mention of prerequisites or edge cases, and no routing to an alternative tool when the bleed is non-uniform or when only a printable area is needed. Usage is only inferable from the phrase 'delivery canvas'.

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.