Skip to main content
Glama

Duplicate HTML IDs

bpj_html_id_uniqueness
Read-onlyIdempotent

Find nonempty ID values used more than once and report source offsets.

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

Input Schema

NameRequiredDescriptionDefault
textYes

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?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds real value beyond that by narrowing scope to nonempty IDs and stating that source offsets are reported, which hints at the output shape. It still omits the 6000-character input limit and whether the scan is limited to a single document.

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 action and the filtering rule, with zero filler. It is efficient, though the extreme brevity is closer to under-specification than to polished conciseness.

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

Completeness4/5

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

Scoring adjusted: for a single-parameter, read-only scan with no output schema, the definition covers the core rule (duplicate nonempty IDs) and the return content (source offsets). The remaining gaps are the input size cap and offset format, which are minor for a tool this simple.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single text parameter, so the description must carry the meaning and it does not. It never explains that the parameter is the raw HTML source to scan or what the maxLength of 6000 implies for behavior on larger documents. An agent learns nothing about the parameter beyond its name.

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 specific verb and resource: it finds nonempty ID values that appear more than once and reports their source offsets. That is concrete enough for an agent to distinguish it from siblings such as bpj_html_duplicate_attributes or the many other single-check HTML audits. It does not explicitly name a sibling to differentiate against, which keeps it just short of a 5.

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 guidance on when to use this tool versus the duplicate-attributes or fragment-target siblings, and no mention of prerequisites. The description does not say the input must be HTML source text or that inputs are capped at 6000 characters, both of which materially affect invocation. Usage is only inferable from the name and the required text parameter.

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.