Skip to main content
Glama

Scan raster dimensions

bpj_design_scan_raster
Read-onlyIdempotent

Calculate the pixel dimensions needed to cover an original at the selected scanning resolution.

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>",
      "ppi": "<ppi>"
    },
    "name": "bpj_design_scan_raster"
  }
}

Input Schema

NameRequiredDescriptionDefault
ppiYes
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds that the result is pixel dimensions derived from original size and resolution, but says nothing about rounding, unit of the result, or failure behavior for out-of-range inputs.

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?

One sentence, front-loaded with the verb and the result, with zero filler. Nothing in it needs to be removed and nothing is buried.

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 simple three-parameter calculator with full annotations and no output schema, the description covers the core computation but omits output units, rounding convention, and input-range consequences. Adequate to attempt a call, but not enough to predict the returned values precisely.

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%, so the description must carry the load; it only loosely gestures at the inputs ("original", "scanning resolution") without mapping them to width, height, and ppi or stating units. The schema titles do supply units (mm, px/in), so the true gap is the lack of any explanation of how the three values combine or whether rounding applies.

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 ("Calculate") and a specific resource ("pixel dimensions needed to cover an original") plus the driving condition ("selected scanning resolution"). It is clearly not a generic dimension tool, though it does not name any sibling calculator such as bpj_design_effective_ppi that an agent might confuse it with.

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 "at the selected scanning resolution" implies a scanning prep workflow, so usage is inferable. But there is no explicit when-to-use/when-not guidance and no pointer to the related resolution or effective-PPI tools, leaving the agent to guess at boundaries.

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.