Skip to main content
Glama

Skip link target review

bpj_html_skip_link_target
Read-onlyIdempotent

Inspect local jumps among the first five links and identify target element types for skip-link review.

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

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 this is a safe, read-only, idempotent, closed-world inspection, so safety needs no repeating. The description adds a genuine behavioral scoping rule — only the first five links are examined — but says nothing about what is reported per link or how the target element types are expressed.

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 compact sentence with the limiting scope ('first five links') stated before the output goal. Dense but not padded; slight compression makes 'local jumps' require a moment of interpretation.

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?

With no output schema and no annotations gap to fill on safety, the description needed to describe the returned result. 'Identify target element types' gestures at the output but leaves unclear whether results are per link, counts, or a list of types, and what counts as a 'local jump'.

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 required parameter, 'text', with 0% schema description coverage and only a 'Source text' title. The description never mentions the parameter, so it does not clarify whether the input is a full HTML document, a fragment, or plain text, nor how the 6000-character limit interacts with document slicing.

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 concrete action (inspect local jumps among the first five links) plus a second concrete output (identify target element types), which is far more specific than the title alone. It does not distinguish itself from the close sibling bpj_html_fragment_targets, so it stops 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The trailing phrase 'for skip-link review' implies the scenario in which this is appropriate, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as bpj_html_fragment_targets. Usage is only implied.

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.