Skip to main content
Glama

HTML fragment target coverage

bpj_html_fragment_targets
Read-onlyIdempotent

Match decoded in-page fragments against element IDs and legacy named anchors in the supplied markup.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the bar is low. The description adds real value by noting 'decoded' fragments and 'legacy named anchors' (implying entity/percent-decoding and pre-HTML5 <a name> support) and by stating the markup is supplied rather than fetched. It says nothing about what unmatched fragments are reported as, but with no output schema that gap is moderate rather than severe.

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, well matched to a one-parameter tool. It is arguably too terse for what it omits, but nothing present is wasted.

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 checker this is close to sufficient, but with no output schema the description should say what the match result contains (matched vs missing targets, duplicate IDs producing the same fragment). As written, an agent knows what to pass but not what comes back.

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?

The schema has one required parameter with 0% description coverage beyond the title 'Source text'. The phrase 'the supplied markup' usefully disambiguates text as HTML source to be scanned, which is genuine added meaning, but the 6000-character cap and any encoding expectations are left entirely to the schema.

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 names a specific verb ('Match') and concrete resources ('decoded in-page fragments', 'element IDs', 'legacy named anchors', 'supplied markup'), so an agent knows it resolves fragment references inside provided HTML. It does not explicitly distinguish itself from close siblings such as bpj_html_id_uniqueness or bpj_html_aria_reference_targets, leaving the boundary to inference.

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, when-not-to-use, or alternative-naming guidance. The agent must infer from the purpose line that this is for validating whether in-page anchors resolve, with no stated prerequisites or exclusions relative to the many other bpj_html_* coverage tools.

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.