Skip to main content
Glama

Link label clarity

bpj_link_label_check
Read-onlyIdempotent

Flag blank or generic labels and repeated labels that lead to different targets.

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": {
      "links": "<links>"
    },
    "name": "bpj_link_label_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, covering the safety profile. The description adds what is being detected but not what counts as 'generic' (e.g. 'click here', 'read more'), whether all findings are returned or only a count, or any output shape – leaving real behavioral questions unanswered.

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 front-loaded sentence with no filler, and the detection rules are ordered clearly. It is efficient, though the economy comes partly from omitting necessary detail rather than from tightness alone.

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

Completeness2/5

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

For a single-parameter check with no output schema and no annotation-level detail about results, the description should at minimum explain the input line format and what a finding looks like. Neither is present, so an agent must guess at formatting and return semantics.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter carries only a title hint ('Link label | target URL per line') with a 5600 maxLength. The description says nothing about the 'label | target' line format, delimiter, or size limit, so it fails to compensate for the near-empty schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a clear verb ('flag') and the conditions checked ('blank or generic labels' and 'repeated labels that lead to different targets'), but it only says 'labels' – the word 'link' lives solely in the name/title, so the sibling distinction against bpj_form_label_check is not carried by the description itself.

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 statement of when to use this tool, no prerequisites, and no pointer to alternatives such as bpj_form_label_check or bpj_new_tab_link_check. The agent must infer from the name that this is an accessibility/QA audit step.

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.