Skip to main content
Glama

Tracking width change

bpj_design_tracking_width
Read-onlyIdempotent

Calculate the added or removed line width for a tracking change in thousandths of an em.

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": {
      "glyphs": "<glyphs>",
      "size": "<size>",
      "tracking": "<tracking>"
    },
    "name": "bpj_design_tracking_width"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYes
glyphsYes
trackingYes

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 establish that this is a safe, read-only, idempotent calculation. The description adds that the result is the added or removed line width in thousandths of an em, but it does not explain rounding, formula behavior, or how the three inputs combine.

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?

The definition is a single, front-loaded sentence with no filler. It communicates the core calculation and output unit efficiently.

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

Completeness2/5

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

For a calculation tool with three required parameters, no parameter descriptions, and no output schema, the description is too sparse. It omits the formula relationship and return-value details that an agent would need to invoke the tool confidently.

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 burden of explaining the three parameters. It only clarifies the tracking unit indirectly and does not explain the roles of glyph count or type size, nor how they affect the calculated line width.

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 gives a clear verb and resource: calculate added or removed line width for a tracking change. It is specific enough to distinguish this as a tracking-width calculation tool, though it does not explicitly differentiate itself from sibling design calculators.

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 description implies the tool is used for tracking changes but does not state when to use it versus alternatives, prerequisites, or exclusions. There is no explicit when-to-use or when-not-to-use guidance.

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.