Skip to main content
Glama

New-tab link attributes

bpj_new_tab_link_check
Read-onlyIdempotent

Check supplied target and rel attributes and suggest explicit tokens for commercial or contributed links.

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": {
      "newTab": "<newTab>",
      "rel": "<rel>",
      "sponsored": "<sponsored>",
      "contributed": "<contributed>"
    },
    "name": "bpj_new_tab_link_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
relYes
newTabYes
sponsoredYes
contributedYes

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, non-destructive and closed-world, so the safety profile is covered. The description adds almost nothing beyond restating the purpose: it does not say what the "check" produces, whether violations are reported as a list, or which tokens are suggested for sponsored versus contributed links.

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 sentence with no filler, and the core resource is front-loaded. Its brevity comes at the cost of precision rather than readability, so it is efficient but slightly cryptic.

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?

With no output schema, 0% schema description coverage, and four required parameters, the description should explain the result shape and the meaning of the booleans. Instead it leaves the agent guessing what a "suggested token" looks like and how the four inputs combine.

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 all four parameters are required, so the description must carry the burden. It references "target" (not a parameter; the schema uses a boolean newTab) and only obliquely maps "commercial or contributed links" to the sponsored/contributed booleans, saying nothing about accepted rel token syntax or the 300-character cap's implications.

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 verb ("Check") and domain (target and rel attributes) are named, and the second clause hints at the outcome ("suggest explicit tokens"). However, "Check" is vague about what is validated and against which rules, and nothing distinguishes this from siblings such as bpj_link_label_check or bpj_canonical_link_check.

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 invoke this tool, no preconditions, and no pointer to any alternative. An agent must infer applicability from the title alone.

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.