Skip to main content
Glama

ARIA ID reference coverage

bpj_html_aria_reference_targets
Read-onlyIdempotent

Validate common ARIA ID references against available IDs 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_aria_reference_targets"
  }
}

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 a safe, local, idempotent read (readOnlyHint, idempotentHint, openWorldHint=false), so the safety profile is covered elsewhere. The description adds that the check is limited to "common" ARIA references and operates on supplied markup, but it does not say whether unresolved references are reported as errors or warnings, nor that input is capped (maxLength 6000) and what happens beyond that.

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, which is appropriate for a one-parameter validator. The hedge word "common" is the only element that costs precision rather than earning its place.

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, the description carries the burden of explaining what the validation returns (unresolved IDs? missing attributes? a count?) and it does not. Annotations cover the safety and locality aspects, but the agent still cannot predict the result shape or the exact set of reference attributes examined.

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 coverage is 0% and the only parameter is labeled just "Source text," so the description's phrase "supplied markup" is the sole signal that this is an HTML string rather than arbitrary prose. That is useful, but it adds nothing about the size cap, whether a full document or fragment is expected, or how the markup is parsed.

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 ("Validate") and a concrete resource ("ARIA ID references against available IDs in the supplied markup"), which tells the agent this is an IDREF-resolution check rather than an inventory. It is distinguishable from siblings like bpj_html_id_uniqueness or bpj_html_fragment_targets by the "ARIA ID references" scope, but it never says which ARIA attributes count as "common," leaving the checked surface fuzzy.

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?

Usage is implied: run it on supplied markup to check ARIA ID references. There is no explicit statement of when to prefer this over bpj_html_id_uniqueness or bpj_html_fragment_targets, no prerequisites, and no note about what this tool does not cover (e.g., non-ARIA references).

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.