Skip to main content
Glama

Dialog naming review

bpj_html_dialog_labels
Read-onlyIdempotent

Inspect native and ARIA dialog elements for explicit aria-label or aria-labelledby attributes.

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": {
      "text": "<text>"
    },
    "name": "bpj_html_dialog_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds the check criteria (explicit aria-label/aria-labelledby only, implicitly excluding e.g. aria-describedby or heading-based naming), which is useful, but it says nothing about what a finding looks like or how results are ordered.

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 padding or repetition of the title. It is efficient, though the brevity leaves the central question — whether findings are elements with labels or elements missing them — unanswered.

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?

There is no output schema, so the description carries the burden of describing return values, and it does not: 'inspect ... for explicit attributes' is ambiguous between listing dialogs that have labels and flagging dialogs that lack them, which is the decisive difference for an accessibility review. For a one-parameter audit tool with no return documentation, this leaves a real gap.

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?

There is one parameter, and schema description coverage is 0%: the schema only gives the title 'Source text' plus a 6000-char cap. The description never mentions the input at all, so the agent must infer from the tool name that 'text' is an HTML fragment containing dialogs, and the length limit's implication (truncation/pagination behavior) is unaddressed.

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 states a specific verb ('Inspect') and resource ('native and ARIA dialog elements') plus the exact attribute set checked ('aria-label or aria-labelledby'). This clearly separates it from sibling label tools that target SVG rather than dialogs, though no sibling is named explicitly.

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 when-to-use statement, no prerequisite, and no mention of when a different review tool (e.g. the SVG label sibling) would be the right call. Usage must be inferred entirely from the tool name and the word 'dialog'.

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.