Skip to main content
Glama

Display pixel pitch

bpj_design_display_pixel_pitch
Read-onlyIdempotent

Estimate square-pixel pitch and display density from diagonal inches and native 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": {
      "pixelsWide": "<pixelsWide>",
      "pixelsHigh": "<pixelsHigh>",
      "diagonal": "<diagonal>"
    },
    "name": "bpj_design_display_pixel_pitch"
  }
}

Input Schema

NameRequiredDescriptionDefault
diagonalYes
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, non-destructive and closed-world, so safety is covered. The description contributes the "square-pixel" assumption and the "estimate" framing, which hint that the result is approximate and assumes non-rectangular-pixel-free panels, but it says nothing about output units 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler; the action and outputs are front-loaded and the input basis follows. Nothing is redundant or padded.

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?

There is no output schema, so the description should specify what comes back (pitch in mm? density in PPI?) and whether both values are returned; it only names them. For a simple three-parameter calculator this is adequate but leaves an agent guessing at result units.

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

Parameters4/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 burden, and it does map prose to all three parameters: diagonal inches to `diagonal` and native resolution to `pixelsWide`/`pixelsHigh`. It could still clarify that width and height are in raw pixels rather than physical units, but the mapping is essentially complete.

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 ("Estimate") plus two concrete outputs (square-pixel pitch and display density) and names the inputs (diagonal inches, native resolution). An agent can tell it computes a physical pixel-size metric, though it does not distinguish itself from the sibling bpj_design_effective_ppi, which plausibly covers similar density ground.

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?

The sentence implies the input context (diagonal + native resolution) but gives no explicit when-to-use, when-not-to-use, or alternative tool. With a near-identical sibling in the catalog, the absence of any routing guidance is a real gap.

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.