Skip to main content
Glama

Duplicate HTML attributes

bpj_html_duplicate_attributes
Read-onlyIdempotent

Identify repeated attribute names per start tag using case-insensitive attribute 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_duplicate_attributes"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one genuine behavioral detail beyond that: matching is case-insensitive and evaluated per start tag, which defines how a duplicate is recognized. It omits any mention of the 6000-character input cap or what a finding contains.

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?

One sentence, front-loaded with the verb and resource, with zero filler. Nothing is wasted, though the terseness means several needed details are simply absent rather than trimmed.

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 check the purpose is sufficient to invoke it, but there is no output schema, so the description should say what a result looks like (e.g., offending attribute name plus tag). It also leaves the input size limit undisclosed, which matters for a 6000-character capped text field.

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 nominally bears the load, but with a single obvious parameter named 'text' and titled 'Source text' the meaning is largely self-evident. The description never mentions the parameter, the 6000-character maximum, or that input must be HTML source, so 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: 'Identify repeated attribute names per start tag,' plus the matching rule (case-insensitive). An agent immediately knows this is an HTML lint check rather than a generic duplicate detector, though it never names a sibling to differentiate from.

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?

The phrase 'per start tag' implies the scope of the check (HTML markup input) but there is no explicit when-to-use, when-not-to-use, or pointer to related sibling checks such as duplicate_key or duplicate_rows. Usage is only inferable from the name and resource.

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.