Skip to main content
Glama

Halftone tonal levels

bpj_design_halftone_levels
Read-onlyIdempotent

Estimate available gray levels for a simple square halftone cell using device dots and screen ruling.

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": {
      "dpi": "<dpi>",
      "lpi": "<lpi>"
    },
    "name": "bpj_design_halftone_levels"
  }
}

Input Schema

NameRequiredDescriptionDefault
dpiYes
lpiYes

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 this read-only, idempotent, closed-world, and non-destructive, so the safety profile is fully covered. The description adds that the model is a simple square cell, but does not disclose the underlying relationship (levels scale with dpi/lpi squared) or whether the result is rounded, so behavior beyond the annotations is only partially described.

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, stating the quantity computed before the inputs. It is efficient, though slightly too terse to cover the rounding and cell-shape assumptions an agent might want.

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 two-parameter calculator with no output schema, the description should say what comes back and in what form; 'gray levels' implies a count but not whether it is a raw count, bits, or a rounded integer. Annotations cover safety, so the remaining gap is output interpretation rather than operational detail.

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 0%, so the description has to carry parameter meaning; it does name the two inputs conceptually as 'device dots' and 'screen ruling', which map to dpi and lpi. However it adds no unit conventions, valid-range intuition, or interaction notes beyond the schema's own titles and min/max 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?

Names a specific verb ('Estimate') and a specific resource ('available gray levels for a simple square halftone cell'), scoped by the inputs used. An agent can tell it is a halftone/tonal-level calculator rather than a grid, PPI, or printable-size tool, though it does not explicitly name a sibling to contrast 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?

Usage is implied by the scope phrase 'simple square halftone cell', which quietly excludes elliptical, round, or multi-cell screens, but there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as effective_ppi for resolution questions.

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.