Skip to main content
Glama

Placed image effective PPI

bpj_design_effective_ppi
Read-onlyIdempotent

Check effective horizontal and vertical densities after placing an image at its final physical size.

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>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "bpj_design_effective_ppi"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYes
heightYes
pixelsHighYes
pixelsWideYes

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: the result is two-dimensional (horizontal AND vertical densities), implying anisotropic output when aspect ratios mismatch. It does not say how out-of-spec results are reported or whether any interpretation/verdict is included.

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 sentence with no filler, front-loaded with the verb and the outputs. It is efficient, though its terseness is part of why parameter and usage details are absent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a pure four-parameter calculator with rich annotations and no output schema, the description covers the essential contract: given pixel dimensions and a final physical size, it returns effective density per axis. The main omissions are unit/mapping clarification and any guidance on interpreting the returned figures.

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 parameter meaning, and it largely does not. It never states that width/height are physical trim dimensions in millimeters while pixelsWide/pixelsHigh are source pixel counts, nor that all four are required; only the schema property titles hint at units. The 'final physical size' phrasing gestures at the pixel-vs-physical split but stops short of mapping it to the 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?

States a specific verb ('Check') and a precise computed resource: effective horizontal and vertical densities after placement at final physical size. An agent can tell this is a resolution/PPI calculator rather than a generic image utility. It does not explicitly distinguish itself from near neighbors like bpj_design_printable_size or bpj_design_macro_image_scale, so sibling differentiation is left implicit.

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 'after placing an image at its final physical size' implies the scenario (post-placement verification), but there is no explicit when-to-use rule, no threshold guidance (e.g., check against 300 PPI for print), and no pointer to alternatives for scaling or fitting. Usage is inferable but not stated.

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.