Skip to main content
Glama

Tiled poster coverage

bpj_design_poster_tiles
Read-onlyIdempotent

Calculate tile rows, columns, and coverage for an assembled poster with overlapping printable sheets.

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": {
      "posterW": "<posterW>",
      "posterH": "<posterH>",
      "sheetW": "<sheetW>",
      "sheetH": "<sheetH>",
      "overlap": "<overlap>"
    },
    "name": "bpj_design_poster_tiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheetHYes
sheetWYes
overlapYes
posterHYes
posterWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered without the description. The description adds genuine domain context — that the calculation models overlapping printable sheets rather than abutted ones — but does not explain the overlap model (per-edge? shared between neighbors?) or what "coverage" measures, which is the most behaviorally meaningful ambiguity here.

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 outputs and the scenario both appear immediately. It is arguably too terse rather than padded — a second sentence on overlap semantics would earn its place.

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 five-required-parameter computation with no output schema, the description lets an agent know roughly what comes back (rows, columns, coverage) but not the shape or units of the result, nor the overlap model. Adequate as a label, incomplete as a specification for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%: the five parameters carry only short titles with mm units, and the description adds no param-level meaning. It references "overlapping printable sheets," hinting that overlap is the inter-sheet overlap in mm, but leaves open whether overlap is per-edge, whether poster dimensions are trimmed or finished size, and how coverage is derived from these inputs.

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 verb ("Calculate") and the exact outputs ("tile rows, columns, and coverage") for a well-defined resource (a poster assembled from overlapping printable sheets). An agent can distinguish this from sibling coverage/design calculators, though no sibling is named 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?

There is no statement of when to use this versus alternatives (e.g., bpj_design_printable_size or bpj_design_bleed_canvas), no prerequisites, and no exclusions. The agent must infer the use case purely from the domain vocabulary in the single sentence.

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.