Skip to main content
Glama

Access key conflicts

bpj_html_accesskey_conflicts
Read-onlyIdempotent

Find accesskey tokens assigned to multiple elements using case-insensitive matching.

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_accesskey_conflicts"
  }
}

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?

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds one genuinely useful behavioral fact — matching is case-insensitive — plus the definition of a conflict (same token on multiple elements). It says nothing about the 6000-char input ceiling, truncation, or what a hit looks like.

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?

One front-loaded sentence with no filler. The matching rule is attached to the action rather than buried, and nothing is repeated from the title or annotations.

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 simple, read-only, single-parameter checker with annotations and no output schema, the description is close to adequate. The remaining gap is what 'text' accepts and the size limit, which matters because input over 6000 characters is rejected.

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 coverage is 0% — the only structured hint is the title 'Source text' and a maxLength. The description never clarifies that the single 'text' parameter is the raw HTML markup to scan, which is the one thing an agent most needs to know. It does not compensate for the coverage gap.

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 ('Find accesskey tokens assigned to multiple elements'), which is enough to distinguish it from the other single-check HTML audit siblings without opening a schema. Slightly short of 5 because it never says the token conflict check is scoped to a single HTML document.

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?

No when-to-use guidance, no prerequisites, and no mention of how it relates to any alternative. The agent must infer that this is a static HTML audit step rather than, say, a duplicate-attribute check.

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.