Skip to main content
Glama

Tap target size check

bpj_tap_target_check
Read-onlyIdempotent

Compare target dimensions with the 24px and 44px WCAG size thresholds.

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

Input Schema

NameRequiredDescriptionDefault
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds the meaningful behavioral fact that two independent thresholds are compared, but it never says what the comparison produces (pass/fail flags per threshold, advisory vs failure) or how the 24px vs 44px results differ in severity.

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. Brevity here is efficiency, not padding, though the terseness leaves the gaps noted in other dimensions.

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?

With no output schema and no parameter descriptions, the description should explain the return shape and how the two thresholds are reported, and it does not. For a simple two-parameter read tool this is a notable omission rather than a minor one.

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 carries the burden, yet it says nothing about width/height beyond restating 'dimensions'. Units (CSS pixels) appear only in schema titles, and it omits important calling semantics such as whether padding/border count toward the measured target or whether a non-square target is evaluated per axis.

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 and resource ('Compare target dimensions') and names the exact reference points (24px and 44px WCAG thresholds), which distinguishes it from sibling accessibility checks like color contrast or form labels. It falls short of 5 only because 'target' is never defined as a clickable/tappable element.

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?

There is no statement of when to use this tool, when not to, or which sibling to prefer for a related accessibility audit. The agent must infer context entirely from the name and thresholds.

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.